← previous blocknext block →recent activity
Analyzing
Block #99,866,568
18 transactions · 14 stateful · 2026-08-28 09:48:05 UTC
Parallelism
78/100
Blocked
29%
Avg conflicts / tx
0.28
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,866,568 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w08w110w212w313w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x16993363…919c
0x34b655…2a6f
4 touches
1 conflict
0x4192c863…5cfa
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x83f3d320…fb59
0x34b655…2a6f
4 touches
1 conflict
0xb2699a97…9c44
0x34b655…2a6f
4 touches
1 conflict
0xb856d1a1…1f18
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity