Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24c8e487c9fd3c5d638da9102b92cac1806aeda40bc7cdef53789b88f794207a

Tx prefix hash: a44c71841539e97d7bbf6ae4bb4f1ade824496cdea2b400c4ffc7f5e1e1f0b37
Tx public key: 6c6a249119d19eb1ba8978fcda2edac5a99dd5ba019bab37191ce6a905481d01
Timestamp: 1735041487 Timestamp [UCT]: 2024-12-24 11:58:07 Age [y:d:h:m:s]: 00:097:01:52:11
Block: 1182139 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69160 RingCT/type: yes/0
Extra: 016c6a249119d19eb1ba8978fcda2edac5a99dd5ba019bab37191ce6a905481d010211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b13b4a5abb1f0d9d652b7772a475124433e3bbc4adc8b8997f1ab38525fb65a9 0.600000000000 1668572 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": 1182149, "vin": [ { "gen": { "height": 1182139 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b13b4a5abb1f0d9d652b7772a475124433e3bbc4adc8b8997f1ab38525fb65a9" } } ], "extra": [ 1, 108, 106, 36, 145, 25, 209, 158, 177, 186, 137, 120, 252, 218, 46, 218, 197, 169, 157, 213, 186, 1, 155, 171, 55, 25, 28, 230, 169, 5, 72, 29, 1, 2, 17, 0, 0, 0, 5, 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