← previous blocknext block →recent activity
Analyzing
Block #100,162,613
35 transactions · 30 stateful · 2026-08-29 10:39:12 UTC
Parallelism
80/100
Blocked
50%
Avg conflicts / tx
1.06
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,162,613 · 35 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
1w05w07w18w29w311w012w113w115w016w119w221w326w327w428w530w531w634w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd2a76d80…ee44
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6426
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x86c070aa…40c8
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x32e6354f…5f73
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xb75d08b2…3e12
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 0xd2a76d80a7…41ee44
Audit this contract →
← previous block·next block →recent activity