← previous blocknext block →recent activity
Analyzing
Block #101,837,328
22 transactions · 21 stateful · 2026-09-04 07:09:05 UTC
Parallelism
64/100
Blocked
57%
Avg conflicts / tx
1.36
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #101,837,328 · 22 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
1w02w14w25w26w27w28w310w412w516w618w720w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xce2afb0d…94be
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x20b1228b…2487
0x34b655…2a6f
6 touches
3 conflicts
0xb575cf74…fbd5
0x34b655…2a6f
6 touches
3 conflicts
0xd7c5728e…0170
0xd32edf…ff58
5 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 0xce2afb0d7d…0794be
Audit this contract →
← previous block·next block →recent activity