Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a09dde5b3a698cb1f90f623aae26666c6cc435821b5272b41f42c3603a153b75

Tx prefix hash: 6bd037ac07ae003b65ab4b167a4ab332794384788d3d2187050326bf50131df0
Tx public key: e00b627878bac3d5cfd0bd8a96d8f83c8dd9427c666e16c33c8fd2a1dd5dca23
Timestamp: 1705677502 Timestamp [UCT]: 2024-01-19 15:18:22 Age [y:d:h:m:s]: 01:332:14:10:45
Block: 938784 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 496572 RingCT/type: yes/0
Extra: 01e00b627878bac3d5cfd0bd8a96d8f83c8dd9427c666e16c33c8fd2a1dd5dca230211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4dfed4cc281b99350796caf2cdfcad21d499183dc7404b443a3d991f6483100 0.600000000000 1396862 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": 938794, "vin": [ { "gen": { "height": 938784 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4dfed4cc281b99350796caf2cdfcad21d499183dc7404b443a3d991f6483100" } } ], "extra": [ 1, 224, 11, 98, 120, 120, 186, 195, 213, 207, 208, 189, 138, 150, 216, 248, 60, 141, 217, 66, 124, 102, 110, 22, 195, 60, 143, 210, 161, 221, 93, 202, 35, 2, 17, 0, 0, 0, 3, 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