← previous blocknext block →recent activity
Analyzing
Block #99,848,715
17 transactions · 15 stateful · 2026-08-28 08:17:59 UTC
Parallelism
82/100
Blocked
33%
Avg conflicts / tx
0.41
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,848,715 · 17 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
1w06w07w18w29w110w213w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf72228f6…970c
0x34b655…2a6f
6 touches
3 conflicts
0xa918f7f0…f410
0x34b655…2a6f
4 touches
1 conflict
0xb6fcbbb7…2b31
0x34b655…2a6f
4 touches
1 conflict
0xe9de869a…06ac
0x34b655…2a6f
4 touches
1 conflict
0x10a5a231…be40
0x34b655…2a6f
4 touches
1 conflict
0x17be1ca8…aca5
0x34b655…2a6f
4 touches
1 conflict
0x3c67d31e…3dbe
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
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 0xf72228f6fd…a6970c
Audit this contract →
← previous block·next block →recent activity