Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a582c358ef8a940362b9682aa0f5213e0304613be938916fc63134e3d0b1890

Tx prefix hash: cf906e666e7891ef9ab3fac12ce0758680ffc4e627a27c0f31f5ef7692fae267
Tx public key: 41925c9deb2512f6c9fe9cfd853d5859b3aa543ec13b00cee1d027a9504a151e
Timestamp: 1721034454 Timestamp [UCT]: 2024-07-15 09:07:34 Age [y:d:h:m:s]: 00:259:09:24:08
Block: 1066143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185300 RingCT/type: yes/0
Extra: 0141925c9deb2512f6c9fe9cfd853d5859b3aa543ec13b00cee1d027a9504a151e02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 99433d928c4c3ca005ca4aaa5960a7165fc714d074ae7d308c77ba2cb74016d6 0.600000000000 1536716 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": 1066153, "vin": [ { "gen": { "height": 1066143 } } ], "vout": [ { "amount": 600000000, "target": { "key": "99433d928c4c3ca005ca4aaa5960a7165fc714d074ae7d308c77ba2cb74016d6" } } ], "extra": [ 1, 65, 146, 92, 157, 235, 37, 18, 246, 201, 254, 156, 253, 133, 61, 88, 89, 179, 170, 84, 62, 193, 59, 0, 206, 225, 208, 39, 169, 80, 74, 21, 30, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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