← previous blocknext block →recent activity
Analyzing
Block #99,867,872
19 transactions · 17 stateful · 2026-08-28 09:54:38 UTC
Parallelism
74/100
Blocked
29%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,867,872 · 19 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
1w07w08w19w212w013w115w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2d20b59b…b4ea
0x34b655…2a6f
8 touches
6 conflicts
0x39ccd26a…4654
0x34b655…2a6f
8 touches
6 conflicts
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x1f396cee…862f
0x34b655…2a6f
4 touches
1 conflict
0x93ffcd76…894e
0x34b655…2a6f
4 touches
1 conflict
0xf72228f6…970c
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0028
0x1b6862…e19c
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
6 conflicts on slot 0x2d20b59b7f…adb4ea
Audit this contract →
← previous block·next block →recent activity