Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01bac33634d220ffba282104dc40bb7ad8d129bb446d7fbc11c31aa6a08bbfe9

Tx prefix hash: 1c4d5aac248a8f489277c57a9178e0357ace52e8bdc70b2ee7d2af685f8a0cc1
Tx public key: 591fbe686da988747af8548e7d8df2aa2869a286bba500abb4c7e69689e90c0a
Timestamp: 1715114212 Timestamp [UCT]: 2024-05-07 20:36:52 Age [y:d:h:m:s]: 00:337:06:48:53
Block: 1017056 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241091 RingCT/type: yes/0
Extra: 01591fbe686da988747af8548e7d8df2aa2869a286bba500abb4c7e69689e90c0a02110000000a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3bba55e0bd4b60c9beebdae59d73d0e485a71fd35e17e5faffa327da9076b9b6 0.600000000000 1480819 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": 1017066, "vin": [ { "gen": { "height": 1017056 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3bba55e0bd4b60c9beebdae59d73d0e485a71fd35e17e5faffa327da9076b9b6" } } ], "extra": [ 1, 89, 31, 190, 104, 109, 169, 136, 116, 122, 248, 84, 142, 125, 141, 242, 170, 40, 105, 162, 134, 187, 165, 0, 171, 180, 199, 230, 150, 137, 233, 12, 10, 2, 17, 0, 0, 0, 10, 122, 156, 244, 199, 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