← previous blocknext block →recent activity
Analyzing
Block #90,617,156
21 transactions · 19 stateful · 2026-07-26 23:30:56 UTC
Parallelism
67/100
Blocked
53%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,617,156 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w06w07w18w29w311w312w413w114w115w517w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xde9d38a8…4c0f
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x3b1ce1dd…dc2f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xdb6a1be2…5afb
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x52f7c71c…d0a6
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
6 conflicts on slot 0xde9d38a88f…994c0f
Audit this contract →
← previous block·next block →recent activity