Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 151b42a001c76817556e437b7abac40ca6c7819955d04a5f8c1d9f36de9a43cb

Tx prefix hash: 9c8124c689b7b7367dcb14a97982b08e69f5e2a2837831a9048f81c99b49ae81
Tx public key: 816c9c8a9630ab67c85f7de3e74680bd495e975a3a640aedd4c16af3d02b98bc
Timestamp: 1754313201 Timestamp [UCT]: 2025-08-04 13:13:21 Age [y:d:h:m:s]: 00:021:07:13:50
Block: 1340106 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 14252 RingCT/type: yes/0
Extra: 01816c9c8a9630ab67c85f7de3e74680bd495e975a3a640aedd4c16af3d02b98bc021100000003b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2af64cc8dde76953a93de05ad1e4711d5e8f8892a3cc7a6ed9548bbe0e41668 0.600000000000 1827923 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": 1340116, "vin": [ { "gen": { "height": 1340106 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2af64cc8dde76953a93de05ad1e4711d5e8f8892a3cc7a6ed9548bbe0e41668" } } ], "extra": [ 1, 129, 108, 156, 138, 150, 48, 171, 103, 200, 95, 125, 227, 231, 70, 128, 189, 73, 94, 151, 90, 58, 100, 10, 237, 212, 193, 106, 243, 208, 43, 152, 188, 2, 17, 0, 0, 0, 3, 178, 247, 132, 196, 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