Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a655125aa473da933122b77f604af7db188aae1a7bee6efd533afff3453da348

Tx prefix hash: cf1772d3191ba1109a087e5364c9bb65292fc180dc0cca12bec436e428b66aae
Tx public key: 65f70bdc221584df96b116dfb8ed8a3efc83eb1057118b8664e091480e01c5b1
Timestamp: 1736766784 Timestamp [UCT]: 2025-01-13 11:13:04 Age [y:d:h:m:s]: 00:124:06:33:38
Block: 1196416 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88625 RingCT/type: yes/0
Extra: 0165f70bdc221584df96b116dfb8ed8a3efc83eb1057118b8664e091480e01c5b10211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f7d5f8d2c05284b67a6bcce1a1b9e53bb66d1740c4c37c50b502f8d39e6acb6 0.600000000000 1683015 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": 1196426, "vin": [ { "gen": { "height": 1196416 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f7d5f8d2c05284b67a6bcce1a1b9e53bb66d1740c4c37c50b502f8d39e6acb6" } } ], "extra": [ 1, 101, 247, 11, 220, 34, 21, 132, 223, 150, 177, 22, 223, 184, 237, 138, 62, 252, 131, 235, 16, 87, 17, 139, 134, 100, 224, 145, 72, 14, 1, 197, 177, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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