Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 160da64ed84df804b08a7cebb9c0d3c7b01bc97259e4d6eb90b1a7dfbd15eecd

Tx prefix hash: 666931c0aa7fd3a6c6843b08fdeecbc6ccf82630e0ce61d250349cdc775feb89
Tx public key: 6b96abb2cc09be600e43b246267600b6ea92d3188b6a0d19484fe1f4a9047c20
Timestamp: 1718709049 Timestamp [UCT]: 2024-06-18 11:10:49 Age [y:d:h:m:s]: 00:314:15:27:20
Block: 1046855 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224871 RingCT/type: yes/0
Extra: 016b96abb2cc09be600e43b246267600b6ea92d3188b6a0d19484fe1f4a9047c2002110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2902e5a8668218e72f82a7296669d2e6cc533467eab0ae364cce97a371504f97 0.600000000000 1516674 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": 1046865, "vin": [ { "gen": { "height": 1046855 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2902e5a8668218e72f82a7296669d2e6cc533467eab0ae364cce97a371504f97" } } ], "extra": [ 1, 107, 150, 171, 178, 204, 9, 190, 96, 14, 67, 178, 70, 38, 118, 0, 182, 234, 146, 211, 24, 139, 106, 13, 25, 72, 79, 225, 244, 169, 4, 124, 32, 2, 17, 0, 0, 0, 3, 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