← previous blocknext block →recent activity
Analyzing
Block #100,080,406
17 transactions · 16 stateful · 2026-08-29 03:45:08 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.82
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,080,406 · 17 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
1w02w16w07w010w111w212w315w416w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc8328065…611a
0x34b655…2a6f
10 touches
10 conflicts
0x5ed1f9d0…fc7f
0x34b655…2a6f
6 touches
3 conflicts
0x739db484…e44a
0x34b655…2a6f
6 touches
3 conflicts
0x31d88d27…7617
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x1e814ad8…7ad2
0x34b655…2a6f
4 touches
1 conflict
0xd895ee0b…d301
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
10 conflicts on slot 0xc83280654f…70611a
Audit this contract →
← previous block·next block →recent activity