← previous blocknext block →recent activity
Analyzing
Block #89,871,808
13 transactions · 11 stateful · 2026-07-24 08:41:03 UTC
Parallelism
85/100
Blocked
27%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,871,808 · 13 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
3w04w05w16w18w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x258fcaf5…2084
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x01df550c…d5de
0x34b655…2a6f
2 touches
0 conflicts
0x1980d4f3…175f
0x34b655…2a6f
2 touches
0 conflicts
0x20081203…b191
0x34b655…2a6f
2 touches
0 conflicts
0x28e9e364…d755
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 0x258fcaf5fc…c22084
Audit this contract →
← previous block·next block →recent activity