Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8ecfa33a1d010d4771b1b70ef2202640def59b5777235a502223f7ddac3a261

Tx prefix hash: bc9f3a67dcba5c562531b80484f8789244cf968c6337f1a4599edd11686981be
Tx public key: 0c0c7cd53ae08968de11a4cc1a77880e6107a5176acfa0047e5f9233e0c140bb
Timestamp: 1714738438 Timestamp [UCT]: 2024-05-03 12:13:58 Age [y:d:h:m:s]: 01:026:17:04:07
Block: 1013942 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280031 RingCT/type: yes/0
Extra: 010c0c7cd53ae08968de11a4cc1a77880e6107a5176acfa0047e5f9233e0c140bb0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34267be7d90df4e5e65154d82a8cb3f3781aa6f168c0f44ed8324bd10f465c9b 0.600000000000 1476893 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": 1013952, "vin": [ { "gen": { "height": 1013942 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34267be7d90df4e5e65154d82a8cb3f3781aa6f168c0f44ed8324bd10f465c9b" } } ], "extra": [ 1, 12, 12, 124, 213, 58, 224, 137, 104, 222, 17, 164, 204, 26, 119, 136, 14, 97, 7, 165, 23, 106, 207, 160, 4, 126, 95, 146, 51, 224, 193, 64, 187, 2, 17, 0, 0, 0, 4, 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