← previous blocknext block →recent activity
Analyzing
Block #100,589,630
38 transactions · 36 stateful · 2026-08-30 22:31:31 UTC
Parallelism
82/100
Blocked
53%
Avg conflicts / tx
1.13
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,589,630 · 38 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
1w03w05w06w17w08w09w110w213w314w415w316w117w222w223w324w325w128w229w430w531w137w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x382434ca…96b5
0x34b655…2a6f
14 touches
21 conflicts
0x2cc5a171…f44d
0x34b655…2a6f
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xde0291c4…ba20
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xd2dfd9bc…3eec
0x34b655…2a6f
6 touches
3 conflicts
0xecd87a39…d9c5
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
21 conflicts on slot 0x382434ca57…4d96b5
Audit this contract →
← previous block·next block →recent activity