← previous blocknext block →recent activity
Analyzing
Block #106,242,195
33 transactions · 32 stateful · 2026-09-19 17:56:03 UTC
Parallelism
70/100
Blocked
69%
Avg conflicts / tx
2.3
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,242,195 · 33 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
1w02w03w14w16w27w312w313w414w516w217w618w719w720w829w531w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7cf3eb0f…06c5
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xd17580f9…ece1
0x754704…b603
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0x524f0872…0d12
0x34b655…2a6f
12 touches
15 conflicts
0x59c2099a…a472
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x5717771c…45ed
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 0x7cf3eb0f68…8806c5
Audit this contract →
← previous block·next block →recent activity