← previous blocknext block →recent activity
Analyzing
Block #106,216,764
22 transactions · 22 stateful · 2026-09-19 15:48:00 UTC
Parallelism
68/100
Blocked
59%
Avg conflicts / tx
1.59
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,216,764 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w27w39w210w011w112w313w414w515w618w319w420w521w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3fc7976e…5f80
0x34b655…2a6f
14 touches
21 conflicts
0xe6040987…df02
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x51fc8795…126f
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x310a7246…2dcb
0x34b655…2a6f
6 touches
3 conflicts
0x7dd96c96…7335
0x34b655…2a6f
6 touches
3 conflicts
0x045532dd…4b7d
0x34b655…2a6f
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 0x3fc7976e40…915f80
Audit this contract →
← previous block·next block →recent activity