← previous blocknext block →recent activity
Analyzing
Block #99,855,067
22 transactions · 21 stateful · 2026-08-28 08:50:00 UTC
Parallelism
86/100
Blocked
33%
Avg conflicts / tx
0.41
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,855,067 · 22 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
1w02w14w05w16w08w110w015w117w018w220w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x62910921…3016
0x34b655…2a6f
6 touches
3 conflicts
0x290abc80…f606
0x34b655…2a6f
4 touches
1 conflict
0x359866c7…de7b
0x34b655…2a6f
4 touches
1 conflict
0x4a830181…d1df
0x34b655…2a6f
4 touches
1 conflict
0x4d971bc9…fadc
0x34b655…2a6f
4 touches
1 conflict
0x69ee34d1…30f8
0x34b655…2a6f
4 touches
1 conflict
0x7b552e2d…fdee
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity