← previous blocknext block →recent activity
Analyzing
Block #89,680,094
6 transactions · 6 stateful · 2026-07-23 16:33:52 UTC
Parallelism
67/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,680,094 · 6 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3e3f27ce…580c
0x34b655…2a6f
4 touches
1 conflict
0x18fb7bf1…a14a
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00d694e4…9835
0x34b655…2a6f
2 touches
0 conflicts
0x0a3dfe51…3b76
0x34b655…2a6f
2 touches
0 conflicts
0x0a3dfe51…3b77
0x34b655…2a6f
2 touches
0 conflicts
0x1da947c4…f74e
0x34b655…2a6f
2 touches
0 conflicts
0x20492d53…80f9
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 0x3e3f27ce6e…b6580c
Audit this contract →
← previous block·next block →recent activity