Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0fc15b3e66f30ae53a6576b9186ecd39688504dc9ea651568820262440d3c3e

Tx prefix hash: 495299e8998097e8c790fd269491f8bea49853f834192b3e2508d157da65eb23
Tx public key: c33f7b5e8d2766ab7c3b632ddcef104063de19ed95291c9e364f6bba2d289bda
Timestamp: 1703395353 Timestamp [UCT]: 2023-12-24 05:22:33 Age [y:d:h:m:s]: 01:133:19:51:40
Block: 919891 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356787 RingCT/type: yes/0
Extra: 01c33f7b5e8d2766ab7c3b632ddcef104063de19ed95291c9e364f6bba2d289bda02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2cc8afe43c10e9a03339cc6acc9b5490b2a513c278ac2884f4b689234cd1aa30 0.600000000000 1377569 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": 919901, "vin": [ { "gen": { "height": 919891 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2cc8afe43c10e9a03339cc6acc9b5490b2a513c278ac2884f4b689234cd1aa30" } } ], "extra": [ 1, 195, 63, 123, 94, 141, 39, 102, 171, 124, 59, 99, 45, 220, 239, 16, 64, 99, 222, 25, 237, 149, 41, 28, 158, 54, 79, 107, 186, 45, 40, 155, 218, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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