Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e77b7dfc36280bcfedc8f4ad4da86e755e3b753d51f6fbd2cc17a34de16dd7d

Tx prefix hash: fd8e9221ce59a8dffd549c0032105569a1f414f7ca6c75089677dce5e434d400
Tx public key: 8b652b7196861b46856f45f6d80f397006774e42b2befba7092f0b66b2b90562
Timestamp: 1645252853 Timestamp [UCT]: 2022-02-19 06:40:53 Age [y:d:h:m:s]: 02:340:00:04:34
Block: 441736 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 762378 RingCT/type: yes/0
Extra: 018b652b7196861b46856f45f6d80f397006774e42b2befba7092f0b66b2b9056202110000000fc9067537000000000000000000

1 output(s) for total of 21.103065628000 dcy

stealth address amount amount idx
00: a8c83acfe4a4eabc56c729de1bb0b106b66788a60d1dfea9219e3e857ecc972c 21.103065628000 854359 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": 441746, "vin": [ { "gen": { "height": 441736 } } ], "vout": [ { "amount": 21103065628, "target": { "key": "a8c83acfe4a4eabc56c729de1bb0b106b66788a60d1dfea9219e3e857ecc972c" } } ], "extra": [ 1, 139, 101, 43, 113, 150, 134, 27, 70, 133, 111, 69, 246, 216, 15, 57, 112, 6, 119, 78, 66, 178, 190, 251, 167, 9, 47, 11, 102, 178, 185, 5, 98, 2, 17, 0, 0, 0, 15, 201, 6, 117, 55, 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