Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 004cb099b0463ae4dd8ce28533a7ce2b111b77a4662fce978405aa6bd0d7d8a8

Tx prefix hash: 8ce282d1e8b2e1d4d956edf0a9cdc587c391a9518ccaebab6e5788cbb065c771
Tx public key: c094d64a8e50e12e721b6421f976c4e19f7719a11705eec8cde1ba0c1a34124a
Timestamp: 1735266758 Timestamp [UCT]: 2024-12-27 02:32:38 Age [y:d:h:m:s]: 00:086:14:17:46
Block: 1183990 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 61691 RingCT/type: yes/0
Extra: 01c094d64a8e50e12e721b6421f976c4e19f7719a11705eec8cde1ba0c1a34124a021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d451bc1afdb1b39dd437933734717000dcfd96d57a4d3d6e7b45c2084e88de2f 0.600000000000 1670441 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": 1184000, "vin": [ { "gen": { "height": 1183990 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d451bc1afdb1b39dd437933734717000dcfd96d57a4d3d6e7b45c2084e88de2f" } } ], "extra": [ 1, 192, 148, 214, 74, 142, 80, 225, 46, 114, 27, 100, 33, 249, 118, 196, 225, 159, 119, 25, 161, 23, 5, 238, 200, 205, 225, 186, 12, 26, 52, 18, 74, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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