Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfa7f9a5e0779cc4026340422079fe7bc9a42ff910b661c9ce3227c983dd061c

Tx prefix hash: 19638a210806099e51bd5cef51f09affda92b7a27f4ad46a5bbe1ad5377a9a66
Tx public key: d43764e5bea422bc1e18016047f3e1802c7cfd4a10f40507ec1c21d22db64248
Timestamp: 1694720880 Timestamp [UCT]: 2023-09-14 19:48:00 Age [y:d:h:m:s]: 01:131:18:52:10
Block: 848163 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355473 RingCT/type: yes/0
Extra: 01d43764e5bea422bc1e18016047f3e1802c7cfd4a10f40507ec1c21d22db642480211000000024b8f5122000000000000000000

1 output(s) for total of 0.949913262000 dcy

stealth address amount amount idx
00: 080b019f9671d778e0ebae5d6c74003cff185299f1a31c1e149e765e5d81d7c9 0.949913262000 1301749 of 0

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": 848173, "vin": [ { "gen": { "height": 848163 } } ], "vout": [ { "amount": 949913262, "target": { "key": "080b019f9671d778e0ebae5d6c74003cff185299f1a31c1e149e765e5d81d7c9" } } ], "extra": [ 1, 212, 55, 100, 229, 190, 164, 34, 188, 30, 24, 1, 96, 71, 243, 225, 128, 44, 124, 253, 74, 16, 244, 5, 7, 236, 28, 33, 210, 45, 182, 66, 72, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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