Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5e395a75d2951aea525675c096878047ec446e3fedbe2e784ed6f2de091d738

Tx prefix hash: 63e65c322cccaed2deb682aa4e3d53558bd604c177efc782f7d9b8182d5fa2d1
Tx public key: 65c30e2eff20f11f3318d25e0a244bc9f4cdcdd533eff8c86e1cd24a12a6ce66
Timestamp: 1714405837 Timestamp [UCT]: 2024-04-29 15:50:37 Age [y:d:h:m:s]: 00:304:18:09:56
Block: 1011176 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217825 RingCT/type: yes/0
Extra: 0165c30e2eff20f11f3318d25e0a244bc9f4cdcdd533eff8c86e1cd24a12a6ce6602110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 79f462ad8aea0ea2298409d97f24791a649d364389d2d7b5bd5541b1c2137679 0.600000000000 1473336 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": 1011186, "vin": [ { "gen": { "height": 1011176 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79f462ad8aea0ea2298409d97f24791a649d364389d2d7b5bd5541b1c2137679" } } ], "extra": [ 1, 101, 195, 14, 46, 255, 32, 241, 31, 51, 24, 210, 94, 10, 36, 75, 201, 244, 205, 205, 213, 51, 239, 248, 200, 110, 28, 210, 74, 18, 166, 206, 102, 2, 17, 0, 0, 0, 9, 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