← previous blocknext block →recent activity
Analyzing
Block #100,917,833
20 transactions · 18 stateful · 2026-09-01 02:02:53 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.85
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,917,833 · 20 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
1w02w16w07w08w19w210w311w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x62b937eb…c75c
0x34b655…2a6f
10 touches
10 conflicts
0x89999c15…fdac
0x34b655…2a6f
8 touches
6 conflicts
0x3be13b22…e859
0x34b655…2a6f
6 touches
3 conflicts
0xcd26fba5…21c6
0x34b655…2a6f
6 touches
3 conflicts
0xdc9915b5…542c
0x34b655…2a6f
6 touches
3 conflicts
0xfc24540b…6463
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x2d071de0…c86e
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 0x62b937eb63…22c75c
Audit this contract →
← previous block·next block →recent activity