Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37a9c0a48766ac0d5f468bc8827869bf982c26603cc956b348b9075af5138ac3

Tx prefix hash: f9d29178c3e6a83727c3afa5cb5163f0229d4cf092ea14e9eea82d49e72c1e33
Tx public key: 70a666f11cd9e9fbf6f63f809cb07dd76295aa62edae5e3a475c248c32873448
Timestamp: 1712007965 Timestamp [UCT]: 2024-04-01 21:46:05 Age [y:d:h:m:s]: 01:080:02:32:48
Block: 991269 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318128 RingCT/type: yes/0
Extra: 0170a666f11cd9e9fbf6f63f809cb07dd76295aa62edae5e3a475c248c3287344802110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c8fc763e806da76755aa576da43dc6102a594036d1ed53f4a87afefa71e10c9 0.600000000000 1451603 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": 991279, "vin": [ { "gen": { "height": 991269 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c8fc763e806da76755aa576da43dc6102a594036d1ed53f4a87afefa71e10c9" } } ], "extra": [ 1, 112, 166, 102, 241, 28, 217, 233, 251, 246, 246, 63, 128, 156, 176, 125, 215, 98, 149, 170, 98, 237, 174, 94, 58, 71, 92, 36, 140, 50, 135, 52, 72, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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