Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a0200ead3c7bc1b2ab232e220378ac51dad6f122bfc46af062756cbaeeab54a

Tx prefix hash: 014606ad96b318b14840f7303f29332310cbb7d0e84566087c1f548422b5f724
Tx public key: 3dec1ff5b1295a0a280bb9ba62950d7914874f8ed0f9eb947eaa854dc314cb1c
Timestamp: 1724796064 Timestamp [UCT]: 2024-08-27 22:01:04 Age [y:d:h:m:s]: 00:291:21:03:51
Block: 1097302 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208430 RingCT/type: yes/0
Extra: 013dec1ff5b1295a0a280bb9ba62950d7914874f8ed0f9eb947eaa854dc314cb1c021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b6ff99a1c05d4fc85fc1eba3c55689a9d7b720045d8c5f85b177d8189993a5a 0.600000000000 1572677 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": 1097312, "vin": [ { "gen": { "height": 1097302 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b6ff99a1c05d4fc85fc1eba3c55689a9d7b720045d8c5f85b177d8189993a5a" } } ], "extra": [ 1, 61, 236, 31, 245, 177, 41, 90, 10, 40, 11, 185, 186, 98, 149, 13, 121, 20, 135, 79, 142, 208, 249, 235, 148, 126, 170, 133, 77, 195, 20, 203, 28, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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