Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 003b07fc661187fbef55c23dd371ff0a1e09e58b8648ab6567b3f20cb12a30a1

Tx prefix hash: e67a9200c1e517c203adba252a0cb39e52c80dbeda84e72d45513b20a360fbd6
Tx public key: 59770c5cf8f545d545186a71ed47710a4eca88af5cc719e6c295f247dcba29e0
Timestamp: 1713168624 Timestamp [UCT]: 2024-04-15 08:10:24 Age [y:d:h:m:s]: 00:269:04:27:50
Block: 1000912 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192692 RingCT/type: yes/0
Extra: 0159770c5cf8f545d545186a71ed47710a4eca88af5cc719e6c295f247dcba29e002110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 24273217f7b67091242f5ba3fce6ae66487a6b5e45788258e98ea15d5a5d854b 0.600000000000 1461412 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": 1000922, "vin": [ { "gen": { "height": 1000912 } } ], "vout": [ { "amount": 600000000, "target": { "key": "24273217f7b67091242f5ba3fce6ae66487a6b5e45788258e98ea15d5a5d854b" } } ], "extra": [ 1, 89, 119, 12, 92, 248, 245, 69, 213, 69, 24, 106, 113, 237, 71, 113, 10, 78, 202, 136, 175, 92, 199, 25, 230, 194, 149, 242, 71, 220, 186, 41, 224, 2, 17, 0, 0, 0, 4, 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