Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65bcafc663b5fd0b73a3beba3175e60d399dd80eb19804fda8d8305cbddc2b73

Tx prefix hash: a6738c7f87a9481669c89410885911adf59d79364fb6b80b4d33bfc069a2dea0
Tx public key: 3eaea5c050778947d9234b1ccb7586074f7fbb6ebadab5bab5428d5c35775157
Timestamp: 1705136167 Timestamp [UCT]: 2024-01-13 08:56:07 Age [y:d:h:m:s]: 01:327:17:02:51
Block: 934300 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 493075 RingCT/type: yes/0
Extra: 013eaea5c050778947d9234b1ccb7586074f7fbb6ebadab5bab5428d5c357751570211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a0549f312cc6037d1c30c4fe533ae75dba49a0b6b8ed550c6f5f307ec63ee23 0.600000000000 1392294 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": 934310, "vin": [ { "gen": { "height": 934300 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a0549f312cc6037d1c30c4fe533ae75dba49a0b6b8ed550c6f5f307ec63ee23" } } ], "extra": [ 1, 62, 174, 165, 192, 80, 119, 137, 71, 217, 35, 75, 28, 203, 117, 134, 7, 79, 127, 187, 110, 186, 218, 181, 186, 181, 66, 141, 92, 53, 119, 81, 87, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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