Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae3ae1fbeae71047c51afbcc1fdd10a9a166bf6ad70363285413cdd98ec810ba

Tx prefix hash: fec73eb712f9066cd3ae5fcfeaa6b951c1f7279e16cbe335080aa10477b18d6f
Tx public key: b4d17442a024c31dcde1fc612f835eb79be327d2fbbb2893a361ec7fcbacff38
Timestamp: 1718540999 Timestamp [UCT]: 2024-06-16 12:29:59 Age [y:d:h:m:s]: 00:284:12:59:00
Block: 1045474 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203315 RingCT/type: yes/0
Extra: 01b4d17442a024c31dcde1fc612f835eb79be327d2fbbb2893a361ec7fcbacff3802110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 62b7df4ac84506153be062cd070463a4914f1c937a2c93537f6bde2aa90523f4 0.600000000000 1515057 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": 1045484, "vin": [ { "gen": { "height": 1045474 } } ], "vout": [ { "amount": 600000000, "target": { "key": "62b7df4ac84506153be062cd070463a4914f1c937a2c93537f6bde2aa90523f4" } } ], "extra": [ 1, 180, 209, 116, 66, 160, 36, 195, 29, 205, 225, 252, 97, 47, 131, 94, 183, 155, 227, 39, 210, 251, 187, 40, 147, 163, 97, 236, 127, 203, 172, 255, 56, 2, 17, 0, 0, 0, 3, 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