Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5a2e74bca7509a2c0872d283b55845718ed9f8617716e7297ecdf3dc7c10179

Tx prefix hash: f39d8a4457a97ef7fc08ceeeb079cd7689aaa2ee765fb696901ee27b1bcdbe5f
Tx public key: 5cfae822b17593f0103587cb0d7e5a4eb4452a50eda23df9b1bf778d0e5417e8
Timestamp: 1735084584 Timestamp [UCT]: 2024-12-24 23:56:24 Age [y:d:h:m:s]: 00:087:13:40:19
Block: 1182496 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62369 RingCT/type: yes/0
Extra: 015cfae822b17593f0103587cb0d7e5a4eb4452a50eda23df9b1bf778d0e5417e80211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a77e69be80094b43ff0d02d0e26e131098320555a7da0a3d1003d0dd18ee3434 0.600000000000 1668931 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": 1182506, "vin": [ { "gen": { "height": 1182496 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a77e69be80094b43ff0d02d0e26e131098320555a7da0a3d1003d0dd18ee3434" } } ], "extra": [ 1, 92, 250, 232, 34, 177, 117, 147, 240, 16, 53, 135, 203, 13, 126, 90, 78, 180, 69, 42, 80, 237, 162, 61, 249, 177, 191, 119, 141, 14, 84, 23, 232, 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