Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de9b87d6451447a15cfa780b209ba2e5718084f4c4638606e4dc94c626489724

Tx prefix hash: abfed09871c9e6b25a07f913b5e73aa103cfc5cf6594d3d3b77a922b1ec34e2b
Tx public key: e682e4ef29d6cdac83649adc35e9c851b9578c46bc7b8c9f74b95bc4540b85d1
Timestamp: 1714009917 Timestamp [UCT]: 2024-04-25 01:51:57 Age [y:d:h:m:s]: 00:305:21:56:23
Block: 1007886 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218666 RingCT/type: yes/0
Extra: 01e682e4ef29d6cdac83649adc35e9c851b9578c46bc7b8c9f74b95bc4540b85d10211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ddf89d788bd53b517ce059ddbf21a6ec889a488dd37bcff42932676ac46d3d1d 0.600000000000 1469352 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": 1007896, "vin": [ { "gen": { "height": 1007886 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ddf89d788bd53b517ce059ddbf21a6ec889a488dd37bcff42932676ac46d3d1d" } } ], "extra": [ 1, 230, 130, 228, 239, 41, 214, 205, 172, 131, 100, 154, 220, 53, 233, 200, 81, 185, 87, 140, 70, 188, 123, 140, 159, 116, 185, 91, 196, 84, 11, 133, 209, 2, 17, 0, 0, 0, 1, 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