Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e20776eacef27caf6b19cdd863a2455eda2ef200f85a9d47e0d314942ae6f14f

Tx prefix hash: 0681f95d0cf4716524a8517ab40409493ea04cd51634f940e83fc75d87611a21
Tx public key: 13ba862ea67e3ac8d9c7fa11aaf0c094c2bac7fd9869b62c645e95e8b488bc86
Timestamp: 1694910966 Timestamp [UCT]: 2023-09-17 00:36:06 Age [y:d:h:m:s]: 01:166:14:43:13
Block: 849745 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 380144 RingCT/type: yes/0
Extra: 0113ba862ea67e3ac8d9c7fa11aaf0c094c2bac7fd9869b62c645e95e8b488bc86021100000001faf35c9c000000000000000000

1 output(s) for total of 0.938516962000 dcy

stealth address amount amount idx
00: cccd129aeeff93cabe554c3529df9dc7574706bed84a67b16ced9a60928b0005 0.938516962000 1303423 of 0

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": 849755, "vin": [ { "gen": { "height": 849745 } } ], "vout": [ { "amount": 938516962, "target": { "key": "cccd129aeeff93cabe554c3529df9dc7574706bed84a67b16ced9a60928b0005" } } ], "extra": [ 1, 19, 186, 134, 46, 166, 126, 58, 200, 217, 199, 250, 17, 170, 240, 192, 148, 194, 186, 199, 253, 152, 105, 182, 44, 100, 94, 149, 232, 180, 136, 188, 134, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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