← previous blocknext block →recent activity
Analyzing
Block #90,786,100
25 transactions · 22 stateful · 2026-07-27 13:40:49 UTC
Parallelism
80/100
Blocked
41%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,786,100 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w16w07w09w010w114w115w016w118w120w221w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb96a99db…95aa
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x0dd44476…ef40
0x34b655…2a6f
4 touches
1 conflict
0x2b7950c1…2342
0x34b655…2a6f
4 touches
1 conflict
0x34f25a23…fb5a
0x34b655…2a6f
4 touches
1 conflict
0x433d8a5a…b11f
0x34b655…2a6f
4 touches
1 conflict
0x4ca2a6c3…ab80
0x34b655…2a6f
4 touches
1 conflict
0x5e47cbde…9659
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 0xb96a99db9e…4095aa
Audit this contract →
← previous block·next block →recent activity