Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20a5ab3e10a859ca1ec18d48ddf580fca7e88561bd2ad5d5245b8d6d8be6c53b

Tx prefix hash: c8e3ecbe3733dd3e75d969b549d8a799ebb53ecd947e131777f04fd0216e4ee7
Tx public key: 113a57da7a11bc4a4124e252fef8adb1c262317ae50afc5dd9d9345ddd6460db
Timestamp: 1681334416 Timestamp [UCT]: 2023-04-12 21:20:16 Age [y:d:h:m:s]: 01:363:06:55:01
Block: 737232 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 520942 RingCT/type: yes/0
Extra: 01113a57da7a11bc4a4124e252fef8adb1c262317ae50afc5dd9d9345ddd6460db0211000000015029cbac000000000000000000

1 output(s) for total of 2.214341331000 dcy

stealth address amount amount idx
00: 4ab873c3d8308678cb4bee193e14951839cc4d1617cbb45f3311381b2a3fdc17 2.214341331000 1183761 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": 737242, "vin": [ { "gen": { "height": 737232 } } ], "vout": [ { "amount": 2214341331, "target": { "key": "4ab873c3d8308678cb4bee193e14951839cc4d1617cbb45f3311381b2a3fdc17" } } ], "extra": [ 1, 17, 58, 87, 218, 122, 17, 188, 74, 65, 36, 226, 82, 254, 248, 173, 177, 194, 98, 49, 122, 229, 10, 252, 93, 217, 217, 52, 93, 221, 100, 96, 219, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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