← previous blocknext block →recent activity
Analyzing
Block #100,752,267
31 transactions · 31 stateful · 2026-08-31 12:09:38 UTC
Parallelism
71/100
Blocked
52%
Avg conflicts / tx
1.58
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #100,752,267 · 31 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w37w28w39w412w213w314w115w416w518w624w725w826w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x81716ce9…095f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0x6e12568b…9a50
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0019
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0029
0x1b6862…e19c
6 touches
3 conflicts
0xb0e4f69d…34e2
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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 0x81716ce924…61095f
Audit this contract →
← previous block·next block →recent activity