Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8fc294a4e5d6309699d3d25c33ed7af5b639440cbf3277f9497ae44e5042517e

Tx prefix hash: 40703b645686d0ac920fa42e19d4b52ea5d7f98859f27b0fef8fd594dcf987d0
Tx public key: ddf1746e5ace2c918b6e318e98d5c9834296d1c72609bf416d8fcaf2639c84e8
Timestamp: 1630806637 Timestamp [UCT]: 2021-09-05 01:50:37 Age [y:d:h:m:s]: 03:115:05:17:25
Block: 327636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 857216 RingCT/type: yes/0
Extra: 01ddf1746e5ace2c918b6e318e98d5c9834296d1c72609bf416d8fcaf2639c84e80211000000190441b428000000000000000000

1 output(s) for total of 50.397195999000 dcy

stealth address amount amount idx
00: dea4bcea11216c2d0d44444a93bc821545677f5da4d634913830814541716827 50.397195999000 678471 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": 327646, "vin": [ { "gen": { "height": 327636 } } ], "vout": [ { "amount": 50397195999, "target": { "key": "dea4bcea11216c2d0d44444a93bc821545677f5da4d634913830814541716827" } } ], "extra": [ 1, 221, 241, 116, 110, 90, 206, 44, 145, 139, 110, 49, 142, 152, 213, 201, 131, 66, 150, 209, 199, 38, 9, 191, 65, 109, 143, 202, 242, 99, 156, 132, 232, 2, 17, 0, 0, 0, 25, 4, 65, 180, 40, 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