Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2af0b0c0cd142fc15e1409a7c6f21636ffacdfad50ac1212dfa8ea45d90e6d8

Tx prefix hash: a4a448f7c34833712e6641802214768b93ea77b748f338b042b647e4b3b5bf03
Tx public key: 074b883e5be7cee27d91b043dd5cc38ae3c71d69f9697a3a7710197ad92ea5a0
Timestamp: 1750730526 Timestamp [UCT]: 2025-06-24 02:02:06 Age [y:d:h:m:s]: 00:150:09:59:32
Block: 1311508 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105426 RingCT/type: yes/0
Extra: 01074b883e5be7cee27d91b043dd5cc38ae3c71d69f9697a3a7710197ad92ea5a0021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 29d3c202929bdaa1e9195f5ab2799ebe0ad037dffe5c39c00ba450417fc800b6 0.600000000000 1799135 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": 1311518, "vin": [ { "gen": { "height": 1311508 } } ], "vout": [ { "amount": 600000000, "target": { "key": "29d3c202929bdaa1e9195f5ab2799ebe0ad037dffe5c39c00ba450417fc800b6" } } ], "extra": [ 1, 7, 75, 136, 62, 91, 231, 206, 226, 125, 145, 176, 67, 221, 92, 195, 138, 227, 199, 29, 105, 249, 105, 122, 58, 119, 16, 25, 122, 217, 46, 165, 160, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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