Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa3a356c811eb7bbfee683554f9a904b2c5f66c1b82526f941c6225a7ef695bf

Tx prefix hash: 152bc64fcef30c80859b169f63f0be6ab3f71c07d8fdeece2239db811679f164
Tx public key: fc7919e429c2e44176095eb67224b74e96d9f5f887dd48f0168db43460f0ba5e
Timestamp: 1583540582 Timestamp [UCT]: 2020-03-07 00:23:02 Age [y:d:h:m:s]: 04:363:12:01:54
Block: 78023 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1153925 RingCT/type: yes/0
Extra: 01fc7919e429c2e44176095eb67224b74e96d9f5f887dd48f0168db43460f0ba5e021100000001a33b4a85000000000000000000

1 output(s) for total of 338.437286983000 dcy

stealth address amount amount idx
00: 1c5ccb3f6789cb308fbe5bb3340ffd5069607e25d32583c7d6c8db1bc5824b98 338.437286983000 143280 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": 78033, "vin": [ { "gen": { "height": 78023 } } ], "vout": [ { "amount": 338437286983, "target": { "key": "1c5ccb3f6789cb308fbe5bb3340ffd5069607e25d32583c7d6c8db1bc5824b98" } } ], "extra": [ 1, 252, 121, 25, 228, 41, 194, 228, 65, 118, 9, 94, 182, 114, 36, 183, 78, 150, 217, 245, 248, 135, 221, 72, 240, 22, 141, 180, 52, 96, 240, 186, 94, 2, 17, 0, 0, 0, 1, 163, 59, 74, 133, 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