Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc71da205d54514fe1712767bcca7c926f1ef6d08a7f4e33a1dadfc8ee5a53df

Tx prefix hash: 76fe37d2ba7b5180138bb156425666b7e203b307aab0ae14266166a03227fa9c
Tx public key: a4172032394694818983e30f45748589e7ea3ca61e2f754ac8d42591c7e32ce2
Timestamp: 1717168387 Timestamp [UCT]: 2024-05-31 15:13:07 Age [y:d:h:m:s]: 00:299:19:22:30
Block: 1034093 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214239 RingCT/type: yes/0
Extra: 01a4172032394694818983e30f45748589e7ea3ca61e2f754ac8d42591c7e32ce202110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83fb92b4d1dc2869ca46a54af1a7401dbfd98eb0dc55f1d5dc1d829af3d0b3a5 0.600000000000 1502566 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": 1034103, "vin": [ { "gen": { "height": 1034093 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83fb92b4d1dc2869ca46a54af1a7401dbfd98eb0dc55f1d5dc1d829af3d0b3a5" } } ], "extra": [ 1, 164, 23, 32, 50, 57, 70, 148, 129, 137, 131, 227, 15, 69, 116, 133, 137, 231, 234, 60, 166, 30, 47, 117, 74, 200, 212, 37, 145, 199, 227, 44, 226, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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