← previous blocknext block →recent activity
Analyzing
Block #92,245,599
19 transactions · 17 stateful · 2026-08-01 16:06:06 UTC
Parallelism
84/100
Blocked
24%
Avg conflicts / tx
0.26
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,245,599 · 19 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
2w03w14w25w26w014w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8e9a7d26…688c
0x34b655…2a6f
4 touches
1 conflict
0xe57232b3…0fbf
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xcc2f3f0f…4689
0xd32edf…ff58
3 touches
1 conflict
0xd6bd849a…5597
0x2a68ba…90c5
2 touches
0 conflicts
0x4e5afb3a…a338
0x3bd359…433a
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 0x8e9a7d26ef…4b688c
Audit this contract →
← previous block·next block →recent activity