← previous blocknext block →recent activity
Analyzing
Block #89,859,312
8 transactions · 8 stateful · 2026-07-24 07:38:12 UTC
Parallelism
75/100
Blocked
25%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,859,312 · 8 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
2w03w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8f63f383…6eda
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x06c2c8c1…c2a9
0x34b655…2a6f
2 touches
0 conflicts
0x09a90ed3…6897
0x34b655…2a6f
2 touches
0 conflicts
0x2fe9992f…4143
0x34b655…2a6f
2 touches
0 conflicts
0x434010de…83fe
0x34b655…2a6f
2 touches
0 conflicts
0x4ca2a6c3…ab80
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: Perpl
1 conflict on slot 0x8f63f383d9…ff6eda
Audit this contract →
← previous block·next block →recent activity