Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 465ff8e3ddfb41189b07b8e12831234b646a792c54d3b02c74aa99c62d2c9f05

Tx prefix hash: e5d1bbc8a22b6b31af8d31a2792f935e37e69352085568b80f87067d23361ad9
Tx public key: cf866cf8e53d87687921eb102d24494bc80c9e076e69888a7a3dc39c9d7626b9
Timestamp: 1718172535 Timestamp [UCT]: 2024-06-12 06:08:55 Age [y:d:h:m:s]: 00:309:10:00:18
Block: 1042415 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221111 RingCT/type: yes/0
Extra: 01cf866cf8e53d87687921eb102d24494bc80c9e076e69888a7a3dc39c9d7626b90211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ccde48683f5fbd36ff3111dcabe2e0160bf917fcfb00901b13da0e06e9fecbd0 0.600000000000 1511328 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": 1042425, "vin": [ { "gen": { "height": 1042415 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ccde48683f5fbd36ff3111dcabe2e0160bf917fcfb00901b13da0e06e9fecbd0" } } ], "extra": [ 1, 207, 134, 108, 248, 229, 61, 135, 104, 121, 33, 235, 16, 45, 36, 73, 75, 200, 12, 158, 7, 110, 105, 136, 138, 122, 61, 195, 156, 157, 118, 38, 185, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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