Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac8b0c31b59e6bcf2a8710646889636f82d583a65a07f9c080e2ab148c9cb49c

Tx prefix hash: 9525c85cd8f6bc5e303ed84b80e952fa69a76dece6c0dba0c57c5a7cf4e56ad3
Tx public key: 88b9df3c1380604968bee86d28bf9b5f0d803ce9080973f009e3552728b89636
Timestamp: 1702458068 Timestamp [UCT]: 2023-12-13 09:01:08 Age [y:d:h:m:s]: 00:337:19:44:37
Block: 912146 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241863 RingCT/type: yes/0
Extra: 0188b9df3c1380604968bee86d28bf9b5f0d803ce9080973f009e3552728b89636021100000008faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd37341c0d5c8e55eae2176a305d8691cf1727d8f393bb8d203bed55881352d9 0.600000000000 1369366 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": 912156, "vin": [ { "gen": { "height": 912146 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd37341c0d5c8e55eae2176a305d8691cf1727d8f393bb8d203bed55881352d9" } } ], "extra": [ 1, 136, 185, 223, 60, 19, 128, 96, 73, 104, 190, 232, 109, 40, 191, 155, 95, 13, 128, 60, 233, 8, 9, 115, 240, 9, 227, 85, 39, 40, 184, 150, 54, 2, 17, 0, 0, 0, 8, 250, 243, 92, 156, 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