Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc3842a3b0157929facd3f84af2b481af041cdf73f76883ff4ebed00b3e91d80

Tx prefix hash: ff3a2baaf5f878f9108e6e2d6a74cf80460c236c05d0712253955ed7e638127e
Tx public key: f3e8610cca3a3dd773c5ee84c8d574bfd71f99d7e34c66ddf0a8ae8c1413269e
Timestamp: 1715726715 Timestamp [UCT]: 2024-05-14 22:45:15 Age [y:d:h:m:s]: 01:003:23:27:23
Block: 1022133 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263750 RingCT/type: yes/0
Extra: 01f3e8610cca3a3dd773c5ee84c8d574bfd71f99d7e34c66ddf0a8ae8c1413269e021100000004c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 505425ba70d05bdf28032195f857f32584a05229a9b9e7651f8e33c862de6d8d 0.600000000000 1486646 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": 1022143, "vin": [ { "gen": { "height": 1022133 } } ], "vout": [ { "amount": 600000000, "target": { "key": "505425ba70d05bdf28032195f857f32584a05229a9b9e7651f8e33c862de6d8d" } } ], "extra": [ 1, 243, 232, 97, 12, 202, 58, 61, 215, 115, 197, 238, 132, 200, 213, 116, 191, 215, 31, 153, 215, 227, 76, 102, 221, 240, 168, 174, 140, 20, 19, 38, 158, 2, 17, 0, 0, 0, 4, 197, 69, 41, 96, 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