Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2bf5c53d2b4bc6eaff95fcebc8ad848a10fe9be439fac35729618b90b6f14f7f

Tx prefix hash: 1d37b79724594236487a1417e79b47fa87f01e362e75f57c5b38054f884886cc
Tx public key: 32033502e526a8a0e69967c477a3356b8d1a6862a025297e3e63edb0ce1387d2
Timestamp: 1751490617 Timestamp [UCT]: 2025-07-02 21:10:17 Age [y:d:h:m:s]: 00:209:21:53:45
Block: 1317468 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148193 RingCT/type: yes/0
Extra: 0132033502e526a8a0e69967c477a3356b8d1a6862a025297e3e63edb0ce1387d2021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f055fb1c2e96f766d269df5b3288e2e419dada3f9fc7b512b0d55a4d38721fe 0.600000000000 1805135 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": 1317478, "vin": [ { "gen": { "height": 1317468 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f055fb1c2e96f766d269df5b3288e2e419dada3f9fc7b512b0d55a4d38721fe" } } ], "extra": [ 1, 50, 3, 53, 2, 229, 38, 168, 160, 230, 153, 103, 196, 119, 163, 53, 107, 141, 26, 104, 98, 160, 37, 41, 126, 62, 99, 237, 176, 206, 19, 135, 210, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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