← previous blocknext block →recent activity
Analyzing
Block #90,540,993
13 transactions · 13 stateful · 2026-07-26 17:07:47 UTC
Parallelism
77/100
Blocked
23%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,540,993 · 13 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
4w06w18w211w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x19e69334…a345
0x34b655…2a6f
4 touches
1 conflict
0x0431e51f…6f91
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x08e8f2c9…a11a
0x34b655…2a6f
4 touches
1 conflict
0x021afc04…da6a
0x34b655…2a6f
2 touches
0 conflicts
0x08cc68a2…2a59
0x34b655…2a6f
2 touches
0 conflicts
0x0a020d6a…36c3
0x34b655…2a6f
2 touches
0 conflicts
0x0c376bba…95b1
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
1 conflict on slot 0x19e6933468…86a345
Audit this contract →
← previous block·next block →recent activity