← previous blocknext block →recent activity
Analyzing
Block #99,367,842
24 transactions · 21 stateful · 2026-08-26 15:44:16 UTC
Parallelism
79/100
Blocked
33%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,367,842 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w05w16w07w28w19w315w116w419w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfa0c5188…06f2
0x34b655…2a6f
8 touches
6 conflicts
0x89ac61bf…9443
0x34b655…2a6f
8 touches
6 conflicts
0x1b579371…80cc
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x877392a7…fd85
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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
6 conflicts on slot 0xfa0c518825…0b06f2
Audit this contract →
← previous block·next block →recent activity