← previous blocknext block →recent activity
Analyzing
Block #100,080,694
22 transactions · 20 stateful · 2026-08-29 03:46:35 UTC
Parallelism
73/100
Blocked
35%
Avg conflicts / tx
0.77
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,080,694 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w16w211w212w313w114w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xa11b60f7…8e8b
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x50c61506…343f
0x34b655…2a6f
6 touches
3 conflicts
0xfc67c406…e655
0x34b655…2a6f
6 touches
3 conflicts
0x29354600…7b17
0x34b655…2a6f
6 touches
3 conflicts
0x7dbb5075…c917
0x34b655…2a6f
4 touches
1 conflict
0x203a33b5…86c2
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
6 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity