← previous blocknext block →recent activity
Analyzing
Block #90,375,236
28 transactions · 25 stateful · 2026-07-26 03:06:30 UTC
Parallelism
89/100
Blocked
32%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,375,236 · 28 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w08w110w011w112w214w215w118w024w025w126w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c09c53e…64b4
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xf46c8478…fa48
0x34b655…2a6f
6 touches
3 conflicts
0x5ea9eca9…22a6
0x34b655…2a6f
4 touches
1 conflict
0x5ea9eca9…22a7
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
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
3 conflicts on slot 0x7c09c53e5b…3864b4
Audit this contract →
← previous block·next block →recent activity