← previous blocknext block →recent activity
Analyzing
Block #100,811,385
35 transactions · 30 stateful · 2026-08-31 17:07:14 UTC
Parallelism
71/100
Blocked
57%
Avg conflicts / tx
1.6
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #100,811,385 · 35 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w06w07w19w110w111w212w313w414w515w618w122w729w831w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
16 touches
28 conflicts
0x07b86c51…cdae
0x2a68ba…90c5
10 touches
10 conflicts
0x11b69a7e…334e
0x01bff4…1071
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0xf5a607fd…d3d4
0x851145…3f07
10 touches
10 conflicts
0x6938f481…8f24
0x34b655…2a6f
8 touches
6 conflicts
0x184e765d…08f6
0x34b655…2a6f
6 touches
3 conflicts
0xbc8fb280…76a3
0x34b655…2a6f
6 touches
3 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
28 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity