Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 220329e8cf2439c67f8e6d818fc762505c4723d7560bd005b11585f6a06d3ccb

Tx prefix hash: 82702bf3847c65e68a363ee6f5ea52a8d200974a9813c4661e7c15550865c9fe
Tx public key: c9bfdf149e0b6ec68e0ff920da6d4d5b128e311221a0251cc73f5883ee31dec8
Timestamp: 1736997257 Timestamp [UCT]: 2025-01-16 03:14:17 Age [y:d:h:m:s]: 00:305:04:44:06
Block: 1198320 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215633 RingCT/type: yes/0
Extra: 01c9bfdf149e0b6ec68e0ff920da6d4d5b128e311221a0251cc73f5883ee31dec80211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 556059ec7b2e344b26b2a3e730d3abda90b01e4ddb1a44a7abac982e6fde1329 0.600000000000 1684943 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": 1198330, "vin": [ { "gen": { "height": 1198320 } } ], "vout": [ { "amount": 600000000, "target": { "key": "556059ec7b2e344b26b2a3e730d3abda90b01e4ddb1a44a7abac982e6fde1329" } } ], "extra": [ 1, 201, 191, 223, 20, 158, 11, 110, 198, 142, 15, 249, 32, 218, 109, 77, 91, 18, 142, 49, 18, 33, 160, 37, 28, 199, 63, 88, 131, 238, 49, 222, 200, 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