← previous blocknext block →recent activity
Analyzing
Block #90,529,508
5 transactions · 5 stateful · 2026-07-26 16:10:01 UTC
Parallelism
40/100
Blocked
40%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,529,508 · 5 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
1w02w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x316644ac…3590
0x34b655…2a6f
4 touches
1 conflict
0xd676e291…3ecf
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x062fb7ca…f691
0x34b655…2a6f
2 touches
0 conflicts
0x0a216284…5e14
0x34b655…2a6f
2 touches
0 conflicts
0x0c69c7b9…996b
0x34b655…2a6f
2 touches
0 conflicts
0x2bfb71b5…3a04
0x34b655…2a6f
2 touches
0 conflicts
0x2bfb71b5…3a05
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 0x316644ac66…dd3590
Audit this contract →
← previous block·next block →recent activity