Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 164220f80d32ad2b9a3322e5dc67bbbe78ae8329de27b3109fe3b2c23bccfdc9

Tx prefix hash: e50f417667ea4196a6c0493fa2205815aafd0a9d4da4652e64216194b6cce779
Tx public key: 1db235096e4bd23cc973f5d8790d7de12aaf86b9d5c5c98f3465897b151b8e55
Timestamp: 1719903182 Timestamp [UCT]: 2024-07-02 06:53:02 Age [y:d:h:m:s]: 00:317:21:51:24
Block: 1056754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227177 RingCT/type: yes/0
Extra: 011db235096e4bd23cc973f5d8790d7de12aaf86b9d5c5c98f3465897b151b8e5502110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96a6bbd75cc99405d2e6f2847ddc0e87923598d714a4c4aed60296b9c475cee3 0.600000000000 1527177 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": 1056764, "vin": [ { "gen": { "height": 1056754 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96a6bbd75cc99405d2e6f2847ddc0e87923598d714a4c4aed60296b9c475cee3" } } ], "extra": [ 1, 29, 178, 53, 9, 110, 75, 210, 60, 201, 115, 245, 216, 121, 13, 125, 225, 42, 175, 134, 185, 213, 197, 201, 143, 52, 101, 137, 123, 21, 27, 142, 85, 2, 17, 0, 0, 0, 3, 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