Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: faef7131d7fbd32d576496efd099c7979e138f0086b8efb7d0df57dee936f792

Tx prefix hash: 0fded60fc82efb4f9ffbe40b6891637bc4cf8be38de90b31bd4a80be2eb4a446
Tx public key: 8fb77b747de99722b4114e9b95a26d067c88d940128d527af4fb367d091e7b24
Timestamp: 1705879919 Timestamp [UCT]: 2024-01-21 23:31:59 Age [y:d:h:m:s]: 01:143:13:40:07
Block: 940462 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363693 RingCT/type: yes/0
Extra: 018fb77b747de99722b4114e9b95a26d067c88d940128d527af4fb367d091e7b2402110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b60d22f4a2e731be035af327754bb0758e63f524d6051daa792ca1db17ee341 0.600000000000 1398600 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": 940472, "vin": [ { "gen": { "height": 940462 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b60d22f4a2e731be035af327754bb0758e63f524d6051daa792ca1db17ee341" } } ], "extra": [ 1, 143, 183, 123, 116, 125, 233, 151, 34, 180, 17, 78, 155, 149, 162, 109, 6, 124, 136, 217, 64, 18, 141, 82, 122, 244, 251, 54, 125, 9, 30, 123, 36, 2, 17, 0, 0, 0, 1, 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