← previous blocknext block →recent activity
Analyzing
Block #100,084,972
23 transactions · 18 stateful · 2026-08-29 04:08:07 UTC
Parallelism
70/100
Blocked
39%
Avg conflicts / tx
0.91
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,084,972 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w012w113w215w316w418w520w622w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb913bb06…49d2
0x34b655…2a6f
12 touches
15 conflicts
0xfb14d7f1…e509
0x34b655…2a6f
12 touches
15 conflicts
0xf06fce24…887d
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x38bcfe5f…6c71
0x34b655…2a6f
6 touches
3 conflicts
0x2d071de0…c86e
0x34b655…2a6f
6 touches
3 conflicts
0x48b13e5e…3c2a
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
15 conflicts on slot 0xb913bb0666…0e49d2
Audit this contract →
← previous block·next block →recent activity