Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 731ece0a608075c693584946cf217f510dd15d762a252233b15214f2b31daa2b

Tx prefix hash: 247e9591c022f245357bfe05a11024941c4775d61d8a63699e9c32fc98c9c5ec
Tx public key: 1a83249fad384a6c09c7667c029ce1ff4b2211e83b5ed30f4ee4d3d4f330ef09
Timestamp: 1714736191 Timestamp [UCT]: 2024-05-03 11:36:31 Age [y:d:h:m:s]: 00:350:03:06:07
Block: 1013925 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250283 RingCT/type: yes/0
Extra: 011a83249fad384a6c09c7667c029ce1ff4b2211e83b5ed30f4ee4d3d4f330ef0902110000000a0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f55d7c5a78754e2fbbc9058861bd652395d0e1394acd8b60a5a827215721dd22 0.600000000000 1476872 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": 1013935, "vin": [ { "gen": { "height": 1013925 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f55d7c5a78754e2fbbc9058861bd652395d0e1394acd8b60a5a827215721dd22" } } ], "extra": [ 1, 26, 131, 36, 159, 173, 56, 74, 108, 9, 199, 102, 124, 2, 156, 225, 255, 75, 34, 17, 232, 59, 94, 211, 15, 78, 228, 211, 212, 243, 48, 239, 9, 2, 17, 0, 0, 0, 10, 0, 17, 5, 91, 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