Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d25ffdb5c1c71febeeed054d8b45028c0475b1cc184f7b968582c60243707a2

Tx prefix hash: 608c6bb5a62090d5ea57867a0f0a514db4d36de8b1802181877c6541ea824761
Tx public key: 8907d3c6c6197fd64ca5f70b8293adf964d43ae975338a02540dacf129e72710
Timestamp: 1720782768 Timestamp [UCT]: 2024-07-12 11:12:48 Age [y:d:h:m:s]: 00:254:21:20:42
Block: 1064057 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182080 RingCT/type: yes/0
Extra: 018907d3c6c6197fd64ca5f70b8293adf964d43ae975338a02540dacf129e7271002110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 60a9745cd08ea51007050fcd356827aa9c62108947637206f3456fd12b12c7f5 0.600000000000 1534580 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": 1064067, "vin": [ { "gen": { "height": 1064057 } } ], "vout": [ { "amount": 600000000, "target": { "key": "60a9745cd08ea51007050fcd356827aa9c62108947637206f3456fd12b12c7f5" } } ], "extra": [ 1, 137, 7, 211, 198, 198, 25, 127, 214, 76, 165, 247, 11, 130, 147, 173, 249, 100, 212, 58, 233, 117, 51, 138, 2, 84, 13, 172, 241, 41, 231, 39, 16, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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