Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 605fb8b700762d2e347662d8737ce40b826da9fe8d5c92d0144d083076daa322

Tx prefix hash: 5c69e02e4ecf3987b671b0e83a113d0fc980d02580e46e1192b12f4439890eec
Tx public key: adc5ab860f01f9802ae9d2493aea781d61575e40670d1d59db4cba0717d76267
Timestamp: 1732659035 Timestamp [UCT]: 2024-11-26 22:10:35 Age [y:d:h:m:s]: 00:133:18:55:46
Block: 1162400 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95435 RingCT/type: yes/0
Extra: 01adc5ab860f01f9802ae9d2493aea781d61575e40670d1d59db4cba0717d762670211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a8469558a90b0397577a61637131dc2a8bb5742cb1018d0e3e58fff8463f8919 0.600000000000 1648055 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": 1162410, "vin": [ { "gen": { "height": 1162400 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8469558a90b0397577a61637131dc2a8bb5742cb1018d0e3e58fff8463f8919" } } ], "extra": [ 1, 173, 197, 171, 134, 15, 1, 249, 128, 42, 233, 210, 73, 58, 234, 120, 29, 97, 87, 94, 64, 103, 13, 29, 89, 219, 76, 186, 7, 23, 215, 98, 103, 2, 17, 0, 0, 0, 2, 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