Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 696ffbab3bc725550e54511e4b4cd3d98764d4da22c74ad7b0c9eaad5f042e8d

Tx prefix hash: 733434596fecb82aab6bc1d375387eb78b0d09e9299982d3de2953e61dd05282
Tx public key: dc006ad930ad1fd9abf1f1c31cbb93f1a041f04ac6c1ba3647f3e14c11b372e1
Timestamp: 1745366651 Timestamp [UCT]: 2025-04-23 00:04:11 Age [y:d:h:m:s]: 00:276:08:27:49
Block: 1267335 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195143 RingCT/type: yes/0
Extra: 01dc006ad930ad1fd9abf1f1c31cbb93f1a041f04ac6c1ba3647f3e14c11b372e1021100000005dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5eb1eb90439cf9e797f86d8c5b2e59d96f4da84c52c593a38500586ace059660 0.600000000000 1754564 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": 1267345, "vin": [ { "gen": { "height": 1267335 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5eb1eb90439cf9e797f86d8c5b2e59d96f4da84c52c593a38500586ace059660" } } ], "extra": [ 1, 220, 0, 106, 217, 48, 173, 31, 217, 171, 241, 241, 195, 28, 187, 147, 241, 160, 65, 240, 74, 198, 193, 186, 54, 71, 243, 225, 76, 17, 179, 114, 225, 2, 17, 0, 0, 0, 5, 219, 181, 113, 193, 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