Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a610d4ca215c77d031917218cf7e4ce92a6ec922ca4776136804a76b151099bb

Tx prefix hash: fc6f4956138073a0cea568649cff0bef2abd603186fb2c9f140ea6fec600b939
Tx public key: 66b8c51427c221962a6380e9aa0d852a0c9642f139b7aa0062931a8a09f07350
Timestamp: 1734143734 Timestamp [UCT]: 2024-12-14 02:35:34 Age [y:d:h:m:s]: 00:123:19:44:37
Block: 1174721 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88278 RingCT/type: yes/0
Extra: 0166b8c51427c221962a6380e9aa0d852a0c9642f139b7aa0062931a8a09f073500211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a457c94b346b8650ada5c1f6bece7aef4c19e1354bff502c86d016f636929c10 0.600000000000 1660908 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": 1174731, "vin": [ { "gen": { "height": 1174721 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a457c94b346b8650ada5c1f6bece7aef4c19e1354bff502c86d016f636929c10" } } ], "extra": [ 1, 102, 184, 197, 20, 39, 194, 33, 150, 42, 99, 128, 233, 170, 13, 133, 42, 12, 150, 66, 241, 57, 183, 170, 0, 98, 147, 26, 138, 9, 240, 115, 80, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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