← previous blocknext block →recent activity
Analyzing
Block #90,285,958
14 transactions · 12 stateful · 2026-07-25 19:30:56 UTC
Parallelism
86/100
Blocked
8%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,285,958 · 14 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
5w06w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x86d1a3fb…ed61
0x34b655…2a6f
4 touches
1 conflict
0x8ec95f2b…f4d7
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x44ed742f…63f5
0x3bd359…433a
2 touches
0 conflicts
0x4eb758b8…b13b
0x3bd359…433a
2 touches
0 conflicts
0xc9d85869…8531
0x3bd359…433a
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 0x86d1a3fb0d…baed61
Audit this contract →
← previous block·next block →recent activity