Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 405a60e58b0549ec63edad4eb2c82295c8056b5ffd862f9e06e107cd94300811

Tx prefix hash: 3d3064677ac342b6df801da92d14d7b04b05c540fd235d7cb75c2ffe8477b8ec
Tx public key: b2de83459003f2565b7f9b1aed847b289e8bed74f2dc6d8327d9b12f8bc24f55
Timestamp: 1718064569 Timestamp [UCT]: 2024-06-11 00:09:29 Age [y:d:h:m:s]: 01:150:03:11:20
Block: 1041518 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365858 RingCT/type: yes/0
Extra: 01b2de83459003f2565b7f9b1aed847b289e8bed74f2dc6d8327d9b12f8bc24f5502110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8cd4099e39bb1b77663a3dbdc9932d2bb89268166f458c5182e04d2854d385ed 0.600000000000 1510213 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": 1041528, "vin": [ { "gen": { "height": 1041518 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8cd4099e39bb1b77663a3dbdc9932d2bb89268166f458c5182e04d2854d385ed" } } ], "extra": [ 1, 178, 222, 131, 69, 144, 3, 242, 86, 91, 127, 155, 26, 237, 132, 123, 40, 158, 139, 237, 116, 242, 220, 109, 131, 39, 217, 177, 47, 139, 194, 79, 85, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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