← previous blocknext block →recent activity
Analyzing
Block #89,749,950
19 transactions · 17 stateful · 2026-07-23 22:26:28 UTC
Parallelism
89/100
Blocked
29%
Avg conflicts / tx
0.32
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,749,950 · 19 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w19w010w111w112w013w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08cc321f…91e1
0x34b655…2a6f
4 touches
1 conflict
0x3df0422c…fd38
0x34b655…2a6f
4 touches
1 conflict
0x3f5831e5…02b2
0x34b655…2a6f
4 touches
1 conflict
0x424934c8…f2f1
0x34b655…2a6f
4 touches
1 conflict
0x48e3acd8…cf41
0x34b655…2a6f
4 touches
1 conflict
0x4c5dc959…73ba
0x34b655…2a6f
4 touches
1 conflict
0x4f999789…32d4
0x34b655…2a6f
4 touches
1 conflict
0x5b37bb6b…aaff
0x34b655…2a6f
4 touches
1 conflict
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: Perpl
1 conflict on slot 0x08cc321f38…d691e1
Audit this contract →
← previous block·next block →recent activity