Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: edbd994bc6584efa7ef9bde0fb076f60a8634fce63bb8dcf6b2b538a78174b4b

Tx prefix hash: d3f0d4ad89498b9fe483c08498d45b35325dbf86a98ca594d08436a2749bfed2
Tx public key: bff0ae1671a68dcd9d1373715f7c885863e77e5e9c8f231cce80b71abc4ae5fb
Timestamp: 1709540569 Timestamp [UCT]: 2024-03-04 08:22:49 Age [y:d:h:m:s]: 01:046:00:25:20
Block: 970851 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293894 RingCT/type: yes/0
Extra: 01bff0ae1671a68dcd9d1373715f7c885863e77e5e9c8f231cce80b71abc4ae5fb0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e632dfd081d65ed7ccea66737a1b8ba1340d410bee278ae7692f4122de97a68 0.600000000000 1430714 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": 970861, "vin": [ { "gen": { "height": 970851 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e632dfd081d65ed7ccea66737a1b8ba1340d410bee278ae7692f4122de97a68" } } ], "extra": [ 1, 191, 240, 174, 22, 113, 166, 141, 205, 157, 19, 115, 113, 95, 124, 136, 88, 99, 231, 126, 94, 156, 143, 35, 28, 206, 128, 183, 26, 188, 74, 229, 251, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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