Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd99f1bb1ac5aba55086166056d1c8b4b9c4877d2855aabefb26f01c37075947

Tx prefix hash: 7f2916b60ac811eb7bc0a6003537b7fe8e369a25bc1d01eeb9e537be2ee76892
Tx public key: bf8fcd21e66f5809eae5d9a01986490405837771dbd282f60be978a7f64b3287
Timestamp: 1708356405 Timestamp [UCT]: 2024-02-19 15:26:45 Age [y:d:h:m:s]: 01:074:19:31:39
Block: 961027 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314504 RingCT/type: yes/0
Extra: 01bf8fcd21e66f5809eae5d9a01986490405837771dbd282f60be978a7f64b32870211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: adf375ba755b19f7d2ed9d11206f065eec86ff7918cc3e28af0bc4750b79c3f5 0.600000000000 1420614 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": 961037, "vin": [ { "gen": { "height": 961027 } } ], "vout": [ { "amount": 600000000, "target": { "key": "adf375ba755b19f7d2ed9d11206f065eec86ff7918cc3e28af0bc4750b79c3f5" } } ], "extra": [ 1, 191, 143, 205, 33, 230, 111, 88, 9, 234, 229, 217, 160, 25, 134, 73, 4, 5, 131, 119, 113, 219, 210, 130, 246, 11, 233, 120, 167, 246, 75, 50, 135, 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