Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a02940d53dbf1bd60c32a43515656b15053149fa502fd5f82634724c2c18694

Tx prefix hash: 51e36d3213284868ff74f100464b89e4b2ea778536549a4a0b44e1f2cee0078e
Tx public key: 4193960a8b985f881fb4cfe80ba8a6a9b315313874a6463a953ad659a6ce4f6d
Timestamp: 1716582049 Timestamp [UCT]: 2024-05-24 20:20:49 Age [y:d:h:m:s]: 00:299:03:16:33
Block: 1029220 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213817 RingCT/type: yes/0
Extra: 014193960a8b985f881fb4cfe80ba8a6a9b315313874a6463a953ad659a6ce4f6d02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21b987639181a32758742b6458423ba2d9d4dc50ad277cdad4fcb74a2aed258f 0.600000000000 1497251 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": 1029230, "vin": [ { "gen": { "height": 1029220 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21b987639181a32758742b6458423ba2d9d4dc50ad277cdad4fcb74a2aed258f" } } ], "extra": [ 1, 65, 147, 150, 10, 139, 152, 95, 136, 31, 180, 207, 232, 11, 168, 166, 169, 179, 21, 49, 56, 116, 166, 70, 58, 149, 58, 214, 89, 166, 206, 79, 109, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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