Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3eaa99055b75c089a5f629dcd6246f8a46f4ab3cb24896f10ed99f461287c0e

Tx prefix hash: 3dae8761a0c517f3f72eb9191eb6d873596b63995c87c3650bfd48fa710878b8
Tx public key: 60fe4d561538951d8dc6bb7affcdf31ab8a2dc0c4d6327e7bb8cfb71d7e3f1d6
Timestamp: 1659604412 Timestamp [UCT]: 2022-08-04 09:13:32 Age [y:d:h:m:s]: 02:283:12:21:52
Block: 558428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 723865 RingCT/type: yes/0
Extra: 0160fe4d561538951d8dc6bb7affcdf31ab8a2dc0c4d6327e7bb8cfb71d7e3f1d6021100000001d834ebe0000000000000000000

1 output(s) for total of 8.663559082000 dcy

stealth address amount amount idx
00: 0a697530a0ab5be4cbbcb73dc57a249167eb9042e5155bf574dc838658afedee 8.663559082000 990506 of 0

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": 558438, "vin": [ { "gen": { "height": 558428 } } ], "vout": [ { "amount": 8663559082, "target": { "key": "0a697530a0ab5be4cbbcb73dc57a249167eb9042e5155bf574dc838658afedee" } } ], "extra": [ 1, 96, 254, 77, 86, 21, 56, 149, 29, 141, 198, 187, 122, 255, 205, 243, 26, 184, 162, 220, 12, 77, 99, 39, 231, 187, 140, 251, 113, 215, 227, 241, 214, 2, 17, 0, 0, 0, 1, 216, 52, 235, 224, 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