← previous blocknext block →recent activity
Analyzing
Block #90,890,688
10 transactions · 10 stateful · 2026-07-27 22:27:07 UTC
Parallelism
60/100
Blocked
40%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,890,688 · 10 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
3w04w15w26w38w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xabf57eb6…416d
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xddbe0a4f…f7b0
0x34b655…2a6f
8 touches
6 conflicts
0x7c51d9aa…af39
0x34b655…2a6f
6 touches
3 conflicts
0x075dcfb7…1c3b
0x34b655…2a6f
6 touches
3 conflicts
0x50dbe610…177f
0x34b655…2a6f
6 touches
3 conflicts
0x79e8f935…c3b6
0x34b655…2a6f
6 touches
3 conflicts
0xc6b9bb4b…145a
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
6 conflicts on slot 0xabf57eb66c…0a416d
Audit this contract →
← previous block·next block →recent activity