Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f4b69d54d06119d2bcc1e37402f2b6beeec9a40edf03118fa271031a3646d06

Tx prefix hash: 3849cd0a88db7d88a0144dd18bb0bae0d9791d6f8f6752a117c05c473a09a0ae
Tx public key: c7e9aefda42cbac2329e9e93bedb738914b41dee1f41d14cbdfcba858bcfc298
Timestamp: 1698288169 Timestamp [UCT]: 2023-10-26 02:42:49 Age [y:d:h:m:s]: 01:083:16:04:52
Block: 877767 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321016 RingCT/type: yes/0
Extra: 01c7e9aefda42cbac2329e9e93bedb738914b41dee1f41d14cbdfcba858bcfc2980211000000034b8f5122000000000000000000

1 output(s) for total of 0.757867994000 dcy

stealth address amount amount idx
00: 8359cdd911f8aca099bcaa137d022c594004c445454eaa2113c5f1f265e73f38 0.757867994000 1333155 of 0

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": 877777, "vin": [ { "gen": { "height": 877767 } } ], "vout": [ { "amount": 757867994, "target": { "key": "8359cdd911f8aca099bcaa137d022c594004c445454eaa2113c5f1f265e73f38" } } ], "extra": [ 1, 199, 233, 174, 253, 164, 44, 186, 194, 50, 158, 158, 147, 190, 219, 115, 137, 20, 180, 29, 238, 31, 65, 209, 76, 189, 252, 186, 133, 139, 207, 194, 152, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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