Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 350207c4ae42fe2422260684229054f84d4767f40afcd6ff5b8607f72237e604

Tx prefix hash: f88ebf091ef645168cb480c324502ffdc80b06c8b19fb75b7effa3b243a1b65d
Tx public key: a781e4fc5a0b5f5c77631fe1af8d6be893a52b254894a503c01e3c5695c33b15
Timestamp: 1718402989 Timestamp [UCT]: 2024-06-14 22:09:49 Age [y:d:h:m:s]: 00:205:10:15:16
Block: 1044317 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147022 RingCT/type: yes/0
Extra: 01a781e4fc5a0b5f5c77631fe1af8d6be893a52b254894a503c01e3c5695c33b1502110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 01b3ca70c3c878c4d1277ebdd6c0a355737fb0c81197836070400a46210870c3 0.600000000000 1513594 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": 1044327, "vin": [ { "gen": { "height": 1044317 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01b3ca70c3c878c4d1277ebdd6c0a355737fb0c81197836070400a46210870c3" } } ], "extra": [ 1, 167, 129, 228, 252, 90, 11, 95, 92, 119, 99, 31, 225, 175, 141, 107, 232, 147, 165, 43, 37, 72, 148, 165, 3, 192, 30, 60, 86, 149, 195, 59, 21, 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