Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 166493235f141d59f1945d017f6a02bcf49d7cdd48676010d9cc5ad891c28776

Tx prefix hash: 7587cb65a7331f83f3975a24cdee382c761f9f573b6eb5d8bb89e768168c21b4
Tx public key: 7f834516e753aa77ba532c730c4c7ab537f0afe980be1d5410f0d28dcc225029
Timestamp: 1734532582 Timestamp [UCT]: 2024-12-18 14:36:22 Age [y:d:h:m:s]: 00:182:02:42:13
Block: 1177951 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129842 RingCT/type: yes/0
Extra: 017f834516e753aa77ba532c730c4c7ab537f0afe980be1d5410f0d28dcc2250290211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef90a2dd1fa75b808d2c43bff81994ea6d295e11242aa7af77945f039cfb74c2 0.600000000000 1664332 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": 1177961, "vin": [ { "gen": { "height": 1177951 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef90a2dd1fa75b808d2c43bff81994ea6d295e11242aa7af77945f039cfb74c2" } } ], "extra": [ 1, 127, 131, 69, 22, 231, 83, 170, 119, 186, 83, 44, 115, 12, 76, 122, 181, 55, 240, 175, 233, 128, 190, 29, 84, 16, 240, 210, 141, 204, 34, 80, 41, 2, 17, 0, 0, 0, 1, 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