← previous blocknext block →recent activity
Analyzing
Block #100,600,961
58 transactions · 32 stateful · 2026-08-30 23:28:31 UTC
Parallelism
86/100
Blocked
69%
Avg conflicts / tx
0.98
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,600,961 · 58 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w17w110w011w113w231w232w333w134w235w244w446w347w448w249w552w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…003d
0x40c49f…2af0
10 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x0d622e34…0000
0x681e90…ae09
8 touches
6 conflicts
0xead15497…1dbe
0x34b655…2a6f
8 touches
6 conflicts
0x0e88bf3a…a7aa
0xd32edf…ff58
7 touches
6 conflicts
0x3f81bcfb…2905
0x40c49f…2af0
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity