Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0fd6e4616522a3a40b74a704a862d5c78a30efe17909607c214d86a3901ab285

Tx prefix hash: 481cbb47ef48e04dd8c2aec8f7232e08a2ea387cf5348b2aa3b4d33a0dbe22ad
Tx public key: 39579c8d336123d3853e0942e587578e9c8bc02310c13cdfb12e1266255ae925
Timestamp: 1705014043 Timestamp [UCT]: 2024-01-11 23:00:43 Age [y:d:h:m:s]: 01:075:19:38:14
Block: 933298 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315278 RingCT/type: yes/0
Extra: 0139579c8d336123d3853e0942e587578e9c8bc02310c13cdfb12e1266255ae9250211000000177a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de518a9303dcb6d5ea1d11bb74577c5dbbae57343e008d222be78c882b1e66f3 0.600000000000 1391260 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": 933308, "vin": [ { "gen": { "height": 933298 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de518a9303dcb6d5ea1d11bb74577c5dbbae57343e008d222be78c882b1e66f3" } } ], "extra": [ 1, 57, 87, 156, 141, 51, 97, 35, 211, 133, 62, 9, 66, 229, 135, 87, 142, 156, 139, 192, 35, 16, 193, 60, 223, 177, 46, 18, 102, 37, 90, 233, 37, 2, 17, 0, 0, 0, 23, 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