Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 8a0ee7ee2a13743adf7a615bf2e01e382a6c36efeea6528461b007cd110b4d33

Tx prefix hash: f25a346f32453ab9708e3e345ca1d056141b873b38aaf4ea42cff5492b7f08b6
Tx public key: b1b2eecc8448c599e10322203fd5e7bacbddce26403008ae94c142277d418649
Timestamp: 1714436016 Timestamp [UCT]: 2024-04-30 00:13:36 Age [y:d:h:m:s]: 01:042:20:34:33
Block: 1011422 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291576 RingCT/type: yes/0
Extra: 01b1b2eecc8448c599e10322203fd5e7bacbddce26403008ae94c142277d4186490211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fdb4d639096f1a7a4d29cb17d4ea2597c3bd1c0e9173ab92866162f1bce38395 0.600000000000 1473648 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1011432, "vin": [ { "gen": { "height": 1011422 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fdb4d639096f1a7a4d29cb17d4ea2597c3bd1c0e9173ab92866162f1bce38395" } } ], "extra": [ 1, 177, 178, 238, 204, 132, 72, 197, 153, 225, 3, 34, 32, 63, 213, 231, 186, 203, 221, 206, 38, 64, 48, 8, 174, 148, 193, 66, 39, 125, 65, 134, 73, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8