Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb2723708ad995ed0a3c8ddfc0f9c21a4c7f3ed0304240e45900a2f9570b7c98

Tx prefix hash: 7894b4ffb3697405a6d3a9044f8bf4317845dcb15ef22e2b2f4422e0d737d9f2
Tx public key: 7d832f6694f4515999e9fa9bd85994d3c46f6e462870ac2f0bc16d93a52437a5
Timestamp: 1724178674 Timestamp [UCT]: 2024-08-20 18:31:14 Age [y:d:h:m:s]: 00:247:01:23:46
Block: 1092207 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176448 RingCT/type: yes/0
Extra: 017d832f6694f4515999e9fa9bd85994d3c46f6e462870ac2f0bc16d93a52437a5021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ed6e8370b9ac4fcbec69f5c44b4baf705b3a18b2137437b9869a22b519824b72 0.600000000000 1566906 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": 1092217, "vin": [ { "gen": { "height": 1092207 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ed6e8370b9ac4fcbec69f5c44b4baf705b3a18b2137437b9869a22b519824b72" } } ], "extra": [ 1, 125, 131, 47, 102, 148, 244, 81, 89, 153, 233, 250, 155, 216, 89, 148, 211, 196, 111, 110, 70, 40, 112, 172, 47, 11, 193, 109, 147, 165, 36, 55, 165, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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