← previous blocknext block →recent activity
Analyzing
Block #100,857,050
26 transactions · 24 stateful · 2026-08-31 20:57:09 UTC
Parallelism
65/100
Blocked
58%
Avg conflicts / tx
1.85
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #100,857,050 · 26 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w26w37w08w413w523w624w725w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1d9154e7…8821
0x34b655…2a6f
16 touches
28 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x2b54cadb…4425
0xd18b7e…414b
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0x340aefa0…855d
0x40c49f…2af0
8 touches
6 conflicts
0x002fed35…79fa
0x2a68ba…90c5
8 touches
6 conflicts
0x8abe290f…8db9
0x34b655…2a6f
6 touches
3 conflicts
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
28 conflicts on slot 0x1d9154e7e4…148821
Audit this contract →
← previous block·next block →recent activity