Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee347c2ef01761ee773c7b2cecd2995cf82b5de8447db08b09a0d3d65ac20d4e

Tx prefix hash: d7a45cc89c86e7bb4bfcb2108b83713e56668aaa21eee1fa1f3c79b24c0f1bf6
Tx public key: 7872b51b5f7fe9003fee3d619d266842def142fad4108638ccc760048b7946b1
Timestamp: 1759740960 Timestamp [UCT]: 2025-10-06 08:56:00 Age [y:d:h:m:s]: 00:096:20:47:05
Block: 1383914 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69357 RingCT/type: yes/0
Extra: 017872b51b5f7fe9003fee3d619d266842def142fad4108638ccc760048b7946b1021100000013a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c77a2d75a751b4acf4e793e814402d8eaaba06fb721b38e6f1721e284950385 0.600000000000 1872063 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": 1383924, "vin": [ { "gen": { "height": 1383914 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c77a2d75a751b4acf4e793e814402d8eaaba06fb721b38e6f1721e284950385" } } ], "extra": [ 1, 120, 114, 181, 27, 95, 127, 233, 0, 63, 238, 61, 97, 157, 38, 104, 66, 222, 241, 66, 250, 212, 16, 134, 56, 204, 199, 96, 4, 139, 121, 70, 177, 2, 17, 0, 0, 0, 19, 165, 220, 205, 121, 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