Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfe7a9d9e6fb54747afd0056bca0b02304cb646660ef030df7da687ca85325db

Tx prefix hash: 448e8ad4bdf05dbd5c0781fea6946357f7d229f1a5dff26b77b1a363f26c1b58
Tx public key: e823f58f5fdb01d84bfe8b3b0ccb7d1c3fe16c3f2274a4b0cc750390cae440b3
Timestamp: 1719517972 Timestamp [UCT]: 2024-06-27 19:52:52 Age [y:d:h:m:s]: 00:308:09:41:36
Block: 1053555 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220387 RingCT/type: yes/0
Extra: 01e823f58f5fdb01d84bfe8b3b0ccb7d1c3fe16c3f2274a4b0cc750390cae440b30211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c89b4e9e70f45f7e7bfe4bb05ab339c3df82094a07b14cafa281c9962b1d2403 0.600000000000 1523902 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": 1053565, "vin": [ { "gen": { "height": 1053555 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c89b4e9e70f45f7e7bfe4bb05ab339c3df82094a07b14cafa281c9962b1d2403" } } ], "extra": [ 1, 232, 35, 245, 143, 95, 219, 1, 216, 75, 254, 139, 59, 12, 203, 125, 28, 63, 225, 108, 63, 34, 116, 164, 176, 204, 117, 3, 144, 202, 228, 64, 179, 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