← previous blocknext block →recent activity
Analyzing
Block #89,770,623
19 transactions · 18 stateful · 2026-07-24 00:10:50 UTC
Parallelism
68/100
Blocked
56%
Avg conflicts / tx
1.21
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,770,623 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w19w010w011w112w113w214w215w316w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92339d95…0800
0x0000a8…8888
12 touches
15 conflicts
0x92339d95…0800
0xb1c8ea…8888
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc4998e49…c79d
0x34b655…2a6f
4 touches
1 conflict
0xf5c75a87…787c
0x34b655…2a6f
4 touches
1 conflict
0xfe2577ac…677b
0x34b655…2a6f
4 touches
1 conflict
0x06c2c8c1…c2a9
0x34b655…2a6f
2 touches
0 conflicts
0x0be3131a…2176
0x34b655…2a6f
2 touches
0 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: 0x0000a8fd…758888
15 conflicts on slot 0x92339d95cd…a80800
Audit this contract →
← previous block·next block →recent activity