Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f69754f5ea013d36daa1a98cd64bf0e0e1d92d0e63e9cf430decb0fccfe12fac

Tx prefix hash: f67f1e381034629bc842d19462c5ac82a5a1a58cd5f3d5681c95a976909083da
Tx public key: f83f9012ac47d889e40a5cdd96b33b44e104d196f6301902d9801dc70e81ab18
Timestamp: 1705136764 Timestamp [UCT]: 2024-01-13 09:06:04 Age [y:d:h:m:s]: 01:046:02:50:38
Block: 934305 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294035 RingCT/type: yes/0
Extra: 01f83f9012ac47d889e40a5cdd96b33b44e104d196f6301902d9801dc70e81ab180211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600040000000 dcy

stealth address amount amount idx
00: e4a48902ce71cdeb7b1e437b841fbdb549e9b34aed005de1e14bea55703d673e 0.600040000000 1392301 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": 934315, "vin": [ { "gen": { "height": 934305 } } ], "vout": [ { "amount": 600040000, "target": { "key": "e4a48902ce71cdeb7b1e437b841fbdb549e9b34aed005de1e14bea55703d673e" } } ], "extra": [ 1, 248, 63, 144, 18, 172, 71, 216, 137, 228, 10, 92, 221, 150, 179, 59, 68, 225, 4, 209, 150, 246, 48, 25, 2, 217, 128, 29, 199, 14, 129, 171, 24, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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