Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee09092bd288c94af49030954f6f71c83961863da45888fdcb52bad5b61bb76c

Tx prefix hash: a35e3e2f3618f2fe65062de3d564193175777b7c767bb0c8ce3c948400e6d0d1
Tx public key: a4c39935bfa9e51612e41a10b472d66a18e45a7bcdbc2492267891723fc04992
Timestamp: 1700261167 Timestamp [UCT]: 2023-11-17 22:46:07 Age [y:d:h:m:s]: 01:148:17:51:03
Block: 893916 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367487 RingCT/type: yes/0
Extra: 01a4c39935bfa9e51612e41a10b472d66a18e45a7bcdbc2492267891723fc04992021100000009e6d27f9c000000000000000000

1 output(s) for total of 0.670016044000 dcy

stealth address amount amount idx
00: 83f261c487d8ddefbedb787f5b408eea4f8e9cde1dff5bc7392aa0ab878006a5 0.670016044000 1350101 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": 893926, "vin": [ { "gen": { "height": 893916 } } ], "vout": [ { "amount": 670016044, "target": { "key": "83f261c487d8ddefbedb787f5b408eea4f8e9cde1dff5bc7392aa0ab878006a5" } } ], "extra": [ 1, 164, 195, 153, 53, 191, 169, 229, 22, 18, 228, 26, 16, 180, 114, 214, 106, 24, 228, 90, 123, 205, 188, 36, 146, 38, 120, 145, 114, 63, 192, 73, 146, 2, 17, 0, 0, 0, 9, 230, 210, 127, 156, 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