← previous blocknext block →recent activity
Analyzing
Block #100,986,762
21 transactions · 19 stateful · 2026-09-01 07:49:37 UTC
Parallelism
76/100
Blocked
47%
Avg conflicts / tx
0.95
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,986,762 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w28w210w011w115w216w317w418w420w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9ab93a0…f656
0x34b655…2a6f
10 touches
10 conflicts
0x7c68d10b…8386
0x34b655…2a6f
8 touches
6 conflicts
0xc7954a60…d294
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x15698ac9…2a46
0x34b655…2a6f
6 touches
3 conflicts
0xdb95e18e…c73d
0x1b6862…e19c
4 touches
1 conflict
0x0a809ce1…7894
0x34b655…2a6f
4 touches
1 conflict
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 0xb9ab93a0c0…6ff656
Audit this contract →
← previous block·next block →recent activity