← previous blocknext block →recent activity
Analyzing
Block #100,160,432
12 transactions · 12 stateful · 2026-08-29 10:28:12 UTC
Parallelism
75/100
Blocked
25%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,160,432 · 12 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w07w110w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x191e0467…70e5
0x34b655…2a6f
6 touches
3 conflicts
0xa02175ba…c0f2
0x8964d7…10f8
4 touches
1 conflict
0x7a66a2b7…8e3e
0x8964d7…10f8
4 touches
1 conflict
0xa02175ba…c0ef
0x8964d7…10f8
4 touches
1 conflict
0xa02175ba…c0f0
0x8964d7…10f8
4 touches
1 conflict
0x57be321f…fecc
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x886db264…846e
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 0x191e0467ba…1470e5
Audit this contract →
← previous block·next block →recent activity