Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c764d194c3aab94140fb7793f22ff6d2fb39f19249ecf450312eed070e93a32f

Tx prefix hash: 48751639c0c09fe29163a60e13858833733bcc16166564410b779f9c876f2893
Tx public key: feb9b6f4a7a239c4dfe34f62622963deaa124d2f299cb49f9c3d41ba8dff65dd
Timestamp: 1736528324 Timestamp [UCT]: 2025-01-10 16:58:44 Age [y:d:h:m:s]: 00:073:00:49:53
Block: 1194436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 51977 RingCT/type: yes/0
Extra: 01feb9b6f4a7a239c4dfe34f62622963deaa124d2f299cb49f9c3d41ba8dff65dd021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 19568b4bf971901b75e9e5b62fafe538f6b1fee55d8ac82aa9062cccf2e9c061 0.600000000000 1681007 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": 1194446, "vin": [ { "gen": { "height": 1194436 } } ], "vout": [ { "amount": 600000000, "target": { "key": "19568b4bf971901b75e9e5b62fafe538f6b1fee55d8ac82aa9062cccf2e9c061" } } ], "extra": [ 1, 254, 185, 182, 244, 167, 162, 57, 196, 223, 227, 79, 98, 98, 41, 99, 222, 170, 18, 77, 47, 41, 156, 180, 159, 156, 61, 65, 186, 141, 255, 101, 221, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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