Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 433f1788a32b2cdddf55cb666c4cca9aa714a014902310d23e4bfe3e00aa82d3

Tx prefix hash: c6b27322df5094337ae7b5a74838f272e4ccefc4c84869679d3eb1eee039ad96
Tx public key: a7be70d5b88d98360911f67ffb8b4dec60a23038a2da42d093a7e0903ade66b3
Timestamp: 1675602079 Timestamp [UCT]: 2023-02-05 13:01:19 Age [y:d:h:m:s]: 02:023:07:23:32
Block: 690361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 538235 RingCT/type: yes/0
Extra: 01a7be70d5b88d98360911f67ffb8b4dec60a23038a2da42d093a7e0903ade66b3021100000002e7ace25d000000000000000000

1 output(s) for total of 3.166265668000 dcy

stealth address amount amount idx
00: f80eeeb578b4bae9548abda3d82b58f93225e174ba7750ba8787abf527a6d49d 3.166265668000 1133083 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": 690371, "vin": [ { "gen": { "height": 690361 } } ], "vout": [ { "amount": 3166265668, "target": { "key": "f80eeeb578b4bae9548abda3d82b58f93225e174ba7750ba8787abf527a6d49d" } } ], "extra": [ 1, 167, 190, 112, 213, 184, 141, 152, 54, 9, 17, 246, 127, 251, 139, 77, 236, 96, 162, 48, 56, 162, 218, 66, 208, 147, 167, 224, 144, 58, 222, 102, 179, 2, 17, 0, 0, 0, 2, 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