← previous blocknext block →recent activity
Analyzing
Block #90,785,357
25 transactions · 22 stateful · 2026-07-27 13:37:05 UTC
Parallelism
68/100
Blocked
41%
Avg conflicts / tx
1.16
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #90,785,357 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w18w09w010w114w218w219w320w421w522w623w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xbf78ee7f…e7fd
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xfb24441a…4183
0x34b655…2a6f
6 touches
3 conflicts
0x48e3acd8…cf41
0x34b655…2a6f
4 touches
1 conflict
0x52c65a03…b027
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity