← previous blocknext block →recent activity
Analyzing
Block #99,625,810
19 transactions · 18 stateful · 2026-08-27 13:30:00 UTC
Parallelism
84/100
Blocked
44%
Avg conflicts / tx
0.63
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,625,810 · 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
1w02w13w26w07w18w110w011w115w216w218w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x261cbea7…e35d
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x261cbea7…e35e
0x34b655…2a6f
6 touches
3 conflicts
0x96ed54e2…04ed
0x34b655…2a6f
6 touches
3 conflicts
0x5d114832…03a4
0x34b655…2a6f
6 touches
3 conflicts
0x0e3d195f…02d1
0xd32edf…ff58
5 touches
3 conflicts
0x38bcfe5f…6c71
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 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity