Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 345df9a60531c7e2b2238099ba86e20da86aeed91c5eb06f296551ebd69cd9fc

Tx prefix hash: 887cd7d37e02869f5779bc232c524b40972507827ddeddb7ceb2c59216dce3ec
Tx public key: 113b0cc7fee0a557bd443c30fb475c4dc694dfd01dc704bb3d8dde625352c490
Timestamp: 1755531339 Timestamp [UCT]: 2025-08-18 15:35:39 Age [y:d:h:m:s]: 00:092:18:02:38
Block: 1349260 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66172 RingCT/type: yes/0
Extra: 01113b0cc7fee0a557bd443c30fb475c4dc694dfd01dc704bb3d8dde625352c49002110000000501491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a65f5d1e7a743aacebeaa68436a809cda2afe15228c3f4e1c883f7d97a7e32d 0.600000000000 1837191 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": 1349270, "vin": [ { "gen": { "height": 1349260 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a65f5d1e7a743aacebeaa68436a809cda2afe15228c3f4e1c883f7d97a7e32d" } } ], "extra": [ 1, 17, 59, 12, 199, 254, 224, 165, 87, 189, 68, 60, 48, 251, 71, 92, 77, 198, 148, 223, 208, 29, 199, 4, 187, 61, 141, 222, 98, 83, 82, 196, 144, 2, 17, 0, 0, 0, 5, 1, 73, 31, 136, 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