← previous blocknext block →recent activity
Analyzing
Block #90,557,364
12 transactions · 10 stateful · 2026-07-26 18:30:08 UTC
Parallelism
67/100
Blocked
30%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,557,364 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x1b49f420…7fe1
0x34b655…2a6f
6 touches
3 conflicts
0x2894b5dd…5c2e
0x34b655…2a6f
6 touches
3 conflicts
0x82bfe0c3…49c9
0x34b655…2a6f
6 touches
3 conflicts
0x17a14264…f419
0x34b655…2a6f
4 touches
1 conflict
0x4efec09e…b41f
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
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 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity