Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94fd2941d069df700c1ac86b1494e8e988aa17ca7a9b36dd3967fff2865026d7

Tx prefix hash: efe5e24e89a11c91c42c5aa240075ab194a73e3e9bcfaeb02e4b46979e67c1c5
Tx public key: 10ae2834215726fde8e4d2cf10102db7955262dd56de3d68fbd7b5689d00465b
Timestamp: 1696073964 Timestamp [UCT]: 2023-09-30 11:39:24 Age [y:d:h:m:s]: 02:037:14:37:46
Block: 859398 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 546496 RingCT/type: yes/0
Extra: 0110ae2834215726fde8e4d2cf10102db7955262dd56de3d68fbd7b5689d00465b0211000000094b8f5122000000000000000000

1 output(s) for total of 0.871882008000 dcy

stealth address amount amount idx
00: d17c01a6d83f19022cec5becff2f93c4f43df575e50372aabdca7a45e3cc2582 0.871882008000 1313624 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": 859408, "vin": [ { "gen": { "height": 859398 } } ], "vout": [ { "amount": 871882008, "target": { "key": "d17c01a6d83f19022cec5becff2f93c4f43df575e50372aabdca7a45e3cc2582" } } ], "extra": [ 1, 16, 174, 40, 52, 33, 87, 38, 253, 232, 228, 210, 207, 16, 16, 45, 183, 149, 82, 98, 221, 86, 222, 61, 104, 251, 215, 181, 104, 157, 0, 70, 91, 2, 17, 0, 0, 0, 9, 75, 143, 81, 34, 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