Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f08f90739fc8a8f7f84d003ee8220e8fd64edbd0dd53d5f5098de5c5597ec21c

Tx prefix hash: 05414ca3527aec47c1bc6f1bdab7552f50ddffad0d1239356e965dfd85f0f32b
Tx public key: 8fd7666e891a089ce16ba7fe4ece5ac930ba14f85848347899c6d7a21a49972d
Timestamp: 1737533215 Timestamp [UCT]: 2025-01-22 08:06:55 Age [y:d:h:m:s]: 00:149:08:46:38
Block: 1202722 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106444 RingCT/type: yes/0
Extra: 018fd7666e891a089ce16ba7fe4ece5ac930ba14f85848347899c6d7a21a49972d0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a5c63ea7bf5b03e1217c9f7f9dc9a03305e0ab6061aa0112a95ef142adadc6e 0.600000000000 1689387 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": 1202732, "vin": [ { "gen": { "height": 1202722 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a5c63ea7bf5b03e1217c9f7f9dc9a03305e0ab6061aa0112a95ef142adadc6e" } } ], "extra": [ 1, 143, 215, 102, 110, 137, 26, 8, 156, 225, 107, 167, 254, 78, 206, 90, 201, 48, 186, 20, 248, 88, 72, 52, 120, 153, 198, 215, 162, 26, 73, 151, 45, 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