Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d70c98fbc3dfea4d09ba269f7157d0d6b554a7831e0e3d8909ce2aeb2b3c49c

Tx prefix hash: cebe1fbd71c460b755ce1806ece4d8a8e57ca0209b354ce128fe316d34ab9b55
Tx public key: f65593639804525df968a5bcfb6a5473da23c1b8485237284ba38a22d32b9e2e
Timestamp: 1712441893 Timestamp [UCT]: 2024-04-06 22:18:13 Age [y:d:h:m:s]: 01:023:05:04:04
Block: 994862 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277596 RingCT/type: yes/0
Extra: 01f65593639804525df968a5bcfb6a5473da23c1b8485237284ba38a22d32b9e2e02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc877c702d37fe1431150b6096f1f4d50447ce04a2c04e181bd768f291031f24 0.600000000000 1455266 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": 994872, "vin": [ { "gen": { "height": 994862 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc877c702d37fe1431150b6096f1f4d50447ce04a2c04e181bd768f291031f24" } } ], "extra": [ 1, 246, 85, 147, 99, 152, 4, 82, 93, 249, 104, 165, 188, 251, 106, 84, 115, 218, 35, 193, 184, 72, 82, 55, 40, 75, 163, 138, 34, 211, 43, 158, 46, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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