Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9cbeda5759231d27f141f389d4c0e88941155edabd778cf9e9894c69369ca9a

Tx prefix hash: c09dbc3f0f141b957bbde444a2bc70ca29094a8b846be9e790cf411f8ce0ff5f
Tx public key: e96f5f99d1e8e6e6ca228fa1aaa47a724d5aa92316f788a3753e01ce331d6377
Timestamp: 1660351802 Timestamp [UCT]: 2022-08-13 00:50:02 Age [y:d:h:m:s]: 02:231:22:12:02
Block: 564594 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 686982 RingCT/type: yes/0
Extra: 01e96f5f99d1e8e6e6ca228fa1aaa47a724d5aa92316f788a3753e01ce331d6377021100000001ec6d1a1a000000000000000000

1 output(s) for total of 8.265436901000 dcy

stealth address amount amount idx
00: 5660cbd9c67336f125f5a88472b6aeb2a04e800233636bd188b2e748cb73a485 8.265436901000 997440 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": 564604, "vin": [ { "gen": { "height": 564594 } } ], "vout": [ { "amount": 8265436901, "target": { "key": "5660cbd9c67336f125f5a88472b6aeb2a04e800233636bd188b2e748cb73a485" } } ], "extra": [ 1, 233, 111, 95, 153, 209, 232, 230, 230, 202, 34, 143, 161, 170, 164, 122, 114, 77, 90, 169, 35, 22, 247, 136, 163, 117, 62, 1, 206, 51, 29, 99, 119, 2, 17, 0, 0, 0, 1, 236, 109, 26, 26, 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