Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 631a89cb0200c18248bd01b47a4e4b4160c4faa515fa3bfd5a596eea8545ca91

Tx prefix hash: 5394a337a399a88df400fdd44b4380182aa92e83e19c357c16c6c679a641cd8c
Tx public key: 6236661e97f7eeb9d256a300a66343c8e50ffd68f5b69476048c512d0243c2ff
Timestamp: 1721100359 Timestamp [UCT]: 2024-07-16 03:25:59 Age [y:d:h:m:s]: 00:248:19:56:10
Block: 1066692 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177744 RingCT/type: yes/0
Extra: 016236661e97f7eeb9d256a300a66343c8e50ffd68f5b69476048c512d0243c2ff02110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 423a68aa3e98987422bbf887f34fc44f12c1a428d4ba4f1374c2eefdddf4e89e 0.600000000000 1537359 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": 1066702, "vin": [ { "gen": { "height": 1066692 } } ], "vout": [ { "amount": 600000000, "target": { "key": "423a68aa3e98987422bbf887f34fc44f12c1a428d4ba4f1374c2eefdddf4e89e" } } ], "extra": [ 1, 98, 54, 102, 30, 151, 247, 238, 185, 210, 86, 163, 0, 166, 99, 67, 200, 229, 15, 253, 104, 245, 182, 148, 118, 4, 140, 81, 45, 2, 67, 194, 255, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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