← previous blocknext block →recent activity
Analyzing
Block #90,040,734
7 transactions · 7 stateful · 2026-07-24 22:51:29 UTC
Parallelism
57/100
Blocked
43%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,040,734 · 7 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
1w02w14w26w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f2d78b1…7363
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x3439dfbc…0d03
0x34b655…2a6f
4 touches
1 conflict
0x1e31292c…8b83
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x388633a0…86cd
0x34b655…2a6f
2 touches
0 conflicts
0x438b7a53…6ae6
0x34b655…2a6f
2 touches
0 conflicts
0x5c5238c6…f2dc
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 0x0f2d78b1bb…5e7363
Audit this contract →
← previous block·next block →recent activity