← previous blocknext block →recent activity
Analyzing
Block #90,810,340
23 transactions · 23 stateful · 2026-07-27 15:42:51 UTC
Parallelism
78/100
Blocked
35%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,810,340 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w18w010w211w012w315w016w118w319w420w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x58d6b9cf…7c9e
0x34b655…2a6f
6 touches
3 conflicts
0xc6000ba5…8d65
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x73320e64…b06f
0x34b655…2a6f
6 touches
3 conflicts
0x0bd95eb4…e562
0x34b655…2a6f
6 touches
3 conflicts
0x41212c1d…88e3
0x34b655…2a6f
4 touches
1 conflict
0x4ac2a863…cba1
0x34b655…2a6f
4 touches
1 conflict
0x5655f5c3…6b75
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
3 conflicts on slot 0x58d6b9cfa8…987c9e
Audit this contract →
← previous block·next block →recent activity