Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1f32153ad4bbc1344b5960db58b53b7dba33401d339ce0d82a632c572feb82f

Tx prefix hash: fe3e9eb235978c931c1b9a24b6c12e0322c227d4f5781d4c336b13bc3015258b
Tx public key: e2ea9d1809a83503d347cb51400dc986746e2c344ec1ab213beb5d9ece1c5ec8
Timestamp: 1725633358 Timestamp [UCT]: 2024-09-06 14:35:58 Age [y:d:h:m:s]: 00:261:00:40:40
Block: 1104264 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186436 RingCT/type: yes/0
Extra: 01e2ea9d1809a83503d347cb51400dc986746e2c344ec1ab213beb5d9ece1c5ec8021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2532c8355e85560879a7083c14498ae45b43e30c3a6c58b1308687dc7bb8992f 0.600000000000 1581343 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": 1104274, "vin": [ { "gen": { "height": 1104264 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2532c8355e85560879a7083c14498ae45b43e30c3a6c58b1308687dc7bb8992f" } } ], "extra": [ 1, 226, 234, 157, 24, 9, 168, 53, 3, 211, 71, 203, 81, 64, 13, 201, 134, 116, 110, 44, 52, 78, 193, 171, 33, 59, 235, 93, 158, 206, 28, 94, 200, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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