← previous blocknext block →recent activity
Analyzing
Block #100,127,972
20 transactions · 18 stateful · 2026-08-29 07:44:38 UTC
Parallelism
70/100
Blocked
50%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,127,972 · 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
3w04w16w210w211w012w113w314w415w416w517w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68e9cd57…b5be
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6426
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…642d
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x4f3a6b4a…3819
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
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
10 conflicts on slot 0x68e9cd57d2…eab5be
Audit this contract →
← previous block·next block →recent activity