← previous blocknext block →recent activity
Analyzing
Block #90,525,389
16 transactions · 13 stateful · 2026-07-26 15:49:18 UTC
Parallelism
81/100
Blocked
31%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,525,389 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w17w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xf2b035ef…4746
0x34b655…2a6f
4 touches
1 conflict
0x1bf8d2af…d140
0x34b655…2a6f
4 touches
1 conflict
0x030bd256…c5c3
0x34b655…2a6f
2 touches
0 conflicts
0x05b26de9…0fd8
0x34b655…2a6f
2 touches
0 conflicts
0x0ae8daac…d4c4
0x34b655…2a6f
2 touches
0 conflicts
0x3a6aab02…1436
0x34b655…2a6f
2 touches
0 conflicts
0x3f098482…fdfb
0x34b655…2a6f
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
3 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity