Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26bf6a57d88b44b4d060ac3229a6f078d1e6103601a83020d58c8340509c5255

Tx prefix hash: 11d6930bb8bfb73a15aa192c7bb7786fb82a67d26b74fb33e364b8f05e00baac
Tx public key: 4f3bd010c3d919aa3dce22c3ae25227b2d91170d8595bda429769dc49f71614d
Timestamp: 1705009776 Timestamp [UCT]: 2024-01-11 21:49:36 Age [y:d:h:m:s]: 01:302:11:04:57
Block: 933260 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 474996 RingCT/type: yes/0
Extra: 014f3bd010c3d919aa3dce22c3ae25227b2d91170d8595bda429769dc49f71614d0211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e43fed721db963a25d9769d6ce51b7a2834c2b68fa7771b68d05354fc5a1ab1d 0.600000000000 1391222 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": 933270, "vin": [ { "gen": { "height": 933260 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e43fed721db963a25d9769d6ce51b7a2834c2b68fa7771b68d05354fc5a1ab1d" } } ], "extra": [ 1, 79, 59, 208, 16, 195, 217, 25, 170, 61, 206, 34, 195, 174, 37, 34, 123, 45, 145, 23, 13, 133, 149, 189, 164, 41, 118, 157, 196, 159, 113, 97, 77, 2, 17, 0, 0, 0, 7, 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