Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d3433c104aeb80215893ea5eefb903a358ff53173e5d6850970b712cb673b06

Tx prefix hash: e7f910b7d332720b01a9a85d329f7687e1ba0a3daccc2f5d6def8dc14e9c3c0d
Tx public key: 2fcca18a29a9b8357180aef8ef791ab5c5170f6b7fc15b23d35a9bdc09481eeb
Timestamp: 1722709398 Timestamp [UCT]: 2024-08-03 18:23:18 Age [y:d:h:m:s]: 00:175:15:16:54
Block: 1080014 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125613 RingCT/type: yes/0
Extra: 012fcca18a29a9b8357180aef8ef791ab5c5170f6b7fc15b23d35a9bdc09481eeb021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9cc9c778022c28b27be7fa7b98f8ccee696e935a1c5920878decf0e898c0aae7 0.600000000000 1553211 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": 1080024, "vin": [ { "gen": { "height": 1080014 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9cc9c778022c28b27be7fa7b98f8ccee696e935a1c5920878decf0e898c0aae7" } } ], "extra": [ 1, 47, 204, 161, 138, 41, 169, 184, 53, 113, 128, 174, 248, 239, 121, 26, 181, 197, 23, 15, 107, 127, 193, 91, 35, 211, 90, 155, 220, 9, 72, 30, 235, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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