Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9938ddd6529552106f02c679969f8b22a16dbb898a4a852771b28c45a632b925

Tx prefix hash: 08e09506648e7cb60731dccee79f50493d4b4ae0fb68481577f332f0de1f9767
Tx public key: b523f836fc02c132c12f6a7698b3bb3943f447e6f7673d160868ae4315cf3adf
Timestamp: 1719002433 Timestamp [UCT]: 2024-06-21 20:40:33 Age [y:d:h:m:s]: 00:270:14:59:04
Block: 1049262 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193414 RingCT/type: yes/0
Extra: 01b523f836fc02c132c12f6a7698b3bb3943f447e6f7673d160868ae4315cf3adf02110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6b49eda43f36f66aeaae6c6f46a4ff48d1f4db30c56eb9389f4f24e3d7c2c959 0.600000000000 1519361 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": 1049272, "vin": [ { "gen": { "height": 1049262 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6b49eda43f36f66aeaae6c6f46a4ff48d1f4db30c56eb9389f4f24e3d7c2c959" } } ], "extra": [ 1, 181, 35, 248, 54, 252, 2, 193, 50, 193, 47, 106, 118, 152, 179, 187, 57, 67, 244, 71, 230, 247, 103, 61, 22, 8, 104, 174, 67, 21, 207, 58, 223, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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