Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62723fd99346502ea4b9e1d43620ea76da3738bde76959b4385da309698594c3

Tx prefix hash: 56e689a3300435381df22f54deb2b4fc1812898b8b707199b6df9a8fa1551196
Tx public key: 7f99f4b3d16a02250199b803655b959a3d9b661036c69cb9a4b14d7fe3b2fa14
Timestamp: 1672206627 Timestamp [UCT]: 2022-12-28 05:50:27 Age [y:d:h:m:s]: 02:112:03:31:03
Block: 662180 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 601868 RingCT/type: yes/0
Extra: 017f99f4b3d16a02250199b803655b959a3d9b661036c69cb9a4b14d7fe3b2fa14021100000004e7ace25d000000000000000000

1 output(s) for total of 3.925750952000 dcy

stealth address amount amount idx
00: 43267b32b08f40ee8ba8d7b8aef1809e6d7c1de3879f047e9e9ab6afb525386c 3.925750952000 1103005 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": 662190, "vin": [ { "gen": { "height": 662180 } } ], "vout": [ { "amount": 3925750952, "target": { "key": "43267b32b08f40ee8ba8d7b8aef1809e6d7c1de3879f047e9e9ab6afb525386c" } } ], "extra": [ 1, 127, 153, 244, 179, 209, 106, 2, 37, 1, 153, 184, 3, 101, 91, 149, 154, 61, 155, 102, 16, 54, 198, 156, 185, 164, 177, 77, 127, 227, 178, 250, 20, 2, 17, 0, 0, 0, 4, 231, 172, 226, 93, 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