← previous blocknext block →recent activity
Analyzing
Block #90,463,212
16 transactions · 14 stateful · 2026-07-26 10:36:29 UTC
Parallelism
63/100
Blocked
64%
Avg conflicts / tx
1.06
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,463,212 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w27w38w49w510w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3a5784b…1b60
0x34b655…2a6f
10 touches
10 conflicts
0x88acffa6…9a44
0x34b655…2a6f
6 touches
3 conflicts
0x6c732992…0af3
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xaff24c74…1161
0x34b655…2a6f
6 touches
3 conflicts
0xb5f244d5…f550
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0xf3a5784b65…671b60
Audit this contract →
← previous block·next block →recent activity