Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8953ae78eac78f2d1f87493126f1eb5481d612efecde66878e1d3b00601e8c67

Tx prefix hash: 334cc48508988ee3e66ecefdf6cca23bc28ff811d38e4ab3d967bd189052d664
Tx public key: 665ee57dafb1adac67dfe6b3e4acc68495276f298b712cf0e7cc09d93f1dd6b6
Timestamp: 1705164339 Timestamp [UCT]: 2024-01-13 16:45:39 Age [y:d:h:m:s]: 01:087:22:11:04
Block: 934544 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323945 RingCT/type: yes/0
Extra: 01665ee57dafb1adac67dfe6b3e4acc68495276f298b712cf0e7cc09d93f1dd6b60211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c34d40bde9c52625af0a2817fe321e7164494160a9387f320830b2ee6e16bc5 0.600000000000 1392558 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": 934554, "vin": [ { "gen": { "height": 934544 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c34d40bde9c52625af0a2817fe321e7164494160a9387f320830b2ee6e16bc5" } } ], "extra": [ 1, 102, 94, 229, 125, 175, 177, 173, 172, 103, 223, 230, 179, 228, 172, 198, 132, 149, 39, 111, 41, 139, 113, 44, 240, 231, 204, 9, 217, 63, 29, 214, 182, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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