← previous blocknext block →recent activity
Analyzing
Block #90,868,212
13 transactions · 13 stateful · 2026-07-27 20:34:04 UTC
Parallelism
54/100
Blocked
38%
Avg conflicts / tx
1.08
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,868,212 · 13 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
2w08w19w210w311w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xd19c9d38…b459
0x34b655…2a6f
6 touches
3 conflicts
0x3727225e…a3cf
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x55955f0b…6085
0x34b655…2a6f
6 touches
3 conflicts
0x10797f0b…439a
0x34b655…2a6f
6 touches
3 conflicts
0xdc568d84…62d9
0x34b655…2a6f
6 touches
3 conflicts
0x6b346db8…48fd
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity