Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80eeb4efc48b9c3dec22a09fff64c3dcc7f5a30c3aee576c89b2b38fb52d1293

Tx prefix hash: fe4bb067ef088cc6f35883cc5d5848fc956a1efac4b3a07531a4420527730874
Tx public key: dab109da043d4d0c1d214413bb2460d1dcf4eabba35aca7247ff3aac63e8de91
Timestamp: 1700539466 Timestamp [UCT]: 2023-11-21 04:04:26 Age [y:d:h:m:s]: 01:177:15:30:57
Block: 896216 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 388159 RingCT/type: yes/0
Extra: 01dab109da043d4d0c1d214413bb2460d1dcf4eabba35aca7247ff3aac63e8de9102110000000175e3f0e9000000000000000000

1 output(s) for total of 0.658361376000 dcy

stealth address amount amount idx
00: 5e586da9c2931b32043890c96076b78bce5d39a4cdfccc1af12c646095e5642a 0.658361376000 1352491 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": 896226, "vin": [ { "gen": { "height": 896216 } } ], "vout": [ { "amount": 658361376, "target": { "key": "5e586da9c2931b32043890c96076b78bce5d39a4cdfccc1af12c646095e5642a" } } ], "extra": [ 1, 218, 177, 9, 218, 4, 61, 77, 12, 29, 33, 68, 19, 187, 36, 96, 209, 220, 244, 234, 187, 163, 90, 202, 114, 71, 255, 58, 172, 99, 232, 222, 145, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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