Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2af1f8a9ea9499c843d161def9c160bfbae41810abaaf56e52eb094c5bf3549

Tx prefix hash: 21ab17263594e00bfea540d026476a2dfdc1d720f35ac46d00efde6ff517b241
Tx public key: 05513e6477188db065b97a9f601686b9bd26f276089b0aef7aa17823dc20cb61
Timestamp: 1725638372 Timestamp [UCT]: 2024-09-06 15:59:32 Age [y:d:h:m:s]: 00:209:09:50:00
Block: 1104302 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149493 RingCT/type: yes/0
Extra: 0105513e6477188db065b97a9f601686b9bd26f276089b0aef7aa17823dc20cb61021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f37bc2d4c4e51f58a92d7ec036c9c154a49929cef4837249c50daa7e49b2f72 0.600000000000 1581391 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": 1104312, "vin": [ { "gen": { "height": 1104302 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f37bc2d4c4e51f58a92d7ec036c9c154a49929cef4837249c50daa7e49b2f72" } } ], "extra": [ 1, 5, 81, 62, 100, 119, 24, 141, 176, 101, 185, 122, 159, 96, 22, 134, 185, 189, 38, 242, 118, 8, 155, 10, 239, 122, 161, 120, 35, 220, 32, 203, 97, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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