← previous blocknext block →recent activity
Analyzing
Block #100,233,597
28 transactions · 22 stateful · 2026-08-29 16:36:29 UTC
Parallelism
64/100
Blocked
59%
Avg conflicts / tx
1.71
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #100,233,597 · 28 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w36w38w410w411w518w419w620w721w524w827w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x044e6274…0db2
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0xa6d40b7f…2969
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0xba5743c7…21c6
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001f
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity