Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8983ad88e0206fe517b502a5b2fa9e2a03dad41ac4a3a02057030b572b823c7e

Tx prefix hash: 180d3918845700ba872ba5457a38a6826671435bb4fe5dda3f9fcea862d784c9
Tx public key: 949d56d824008f8a92f9a95ccd61fb9911c96789af217c6a7bda223dfff8d9b0
Timestamp: 1700474104 Timestamp [UCT]: 2023-11-20 09:55:04 Age [y:d:h:m:s]: 01:209:07:29:10
Block: 895680 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 410705 RingCT/type: yes/0
Extra: 01949d56d824008f8a92f9a95ccd61fb9911c96789af217c6a7bda223dfff8d9b00211000000024b8f5122000000000000000000

1 output(s) for total of 0.661059172000 dcy

stealth address amount amount idx
00: e82f97d0698a57ce391bf5f709f0563227410f3abe96fbec7564ab97e866fa48 0.661059172000 1351921 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": 895690, "vin": [ { "gen": { "height": 895680 } } ], "vout": [ { "amount": 661059172, "target": { "key": "e82f97d0698a57ce391bf5f709f0563227410f3abe96fbec7564ab97e866fa48" } } ], "extra": [ 1, 148, 157, 86, 216, 36, 0, 143, 138, 146, 249, 169, 92, 205, 97, 251, 153, 17, 201, 103, 137, 175, 33, 124, 106, 123, 218, 34, 61, 255, 248, 217, 176, 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