← previous blocknext block →recent activity
Analyzing
Block #89,555,124
18 transactions · 16 stateful · 2026-07-23 03:16:24 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.56
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,555,124 · 18 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
3w05w06w19w210w311w012w116w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5502e1cc…3910
0x34b655…2a6f
6 touches
3 conflicts
0x1fbd24c7…325b
0x34b655…2a6f
4 touches
1 conflict
0x459cbb60…8957
0x34b655…2a6f
4 touches
1 conflict
0x4d58476d…3e80
0x34b655…2a6f
4 touches
1 conflict
0x60a536a6…ef7a
0x34b655…2a6f
4 touches
1 conflict
0x62b26c37…87d6
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x767799cd…f423
0xc8689a…ee79
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
3 conflicts on slot 0x5502e1cc19…1a3910
Audit this contract →
← previous block·next block →recent activity