← previous blocknext block →recent activity
Analyzing
Block #90,611,738
7 transactions · 7 stateful · 2026-07-26 23:03:40 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,611,738 · 7 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1f396cee…862f
0x34b655…2a6f
4 touches
1 conflict
0xa03c2a35…52e6
0x34b655…2a6f
4 touches
1 conflict
0xa4d9c056…538b
0x34b655…2a6f
4 touches
1 conflict
0xcc40b75f…da7f
0x34b655…2a6f
4 touches
1 conflict
0xcf90229a…2f28
0x34b655…2a6f
4 touches
1 conflict
0xf68d5887…d39d
0x34b655…2a6f
4 touches
1 conflict
0x0bcbbcad…fc9c
0x34b655…2a6f
2 touches
0 conflicts
0x0c53719e…0366
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 0x1f396cee30…ac862f
Audit this contract →
← previous block·next block →recent activity