← previous blocknext block →recent activity
Analyzing
Block #100,111,550
16 transactions · 16 stateful · 2026-08-29 06:21:56 UTC
Parallelism
75/100
Blocked
31%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,111,550 · 16 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
3w04w16w08w19w210w315w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x28fe17d2…4cc0
0x34b655…2a6f
6 touches
3 conflicts
0x7bef9f87…a533
0x34b655…2a6f
6 touches
3 conflicts
0x676f9f01…a8ac
0x34b655…2a6f
4 touches
1 conflict
0x6e6a8155…9636
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe0b1cd46…f355
0x34b655…2a6f
4 touches
1 conflict
0xf4e96d0d…91ac
0x34b655…2a6f
4 touches
1 conflict
0x1d9867ad…6d9a
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 0x28fe17d2d3…f04cc0
Audit this contract →
← previous block·next block →recent activity