Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b0dba38842bb38ef7c824f3a5678844ab4cec7e2d9f03ff1c75cc948e31dfb5

Tx prefix hash: f26e16acfd3dea798054522b08f5613cf8d6a0f297f88876313ed54f16afb959
Tx public key: d2044c6b9ab185bab8b1e83e1dbd9c0f2d0619088602722901af39147e6ad17f
Timestamp: 1752511996 Timestamp [UCT]: 2025-07-14 16:53:16 Age [y:d:h:m:s]: 00:172:09:23:32
Block: 1325443 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122006 RingCT/type: yes/0
Extra: 01d2044c6b9ab185bab8b1e83e1dbd9c0f2d0619088602722901af39147e6ad17f02110000000425a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f698b1d8f70849a733343c63f0c52f1e8fd6e6ad0f3c23b4796733b9068689a 0.600000000000 1813188 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": 1325453, "vin": [ { "gen": { "height": 1325443 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f698b1d8f70849a733343c63f0c52f1e8fd6e6ad0f3c23b4796733b9068689a" } } ], "extra": [ 1, 210, 4, 76, 107, 154, 177, 133, 186, 184, 177, 232, 62, 29, 189, 156, 15, 45, 6, 25, 8, 134, 2, 114, 41, 1, 175, 57, 20, 126, 106, 209, 127, 2, 17, 0, 0, 0, 4, 37, 163, 90, 15, 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