← previous blocknext block →recent activity
Analyzing
Block #106,930,936
22 transactions · 22 stateful · 2026-09-22 03:43:27 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
1.59
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,930,936 · 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
1w02w03w16w17w18w29w314w415w516w620w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb8185207…6ccc
0x34b655…2a6f
14 touches
21 conflicts
0x704a8131…bbe8
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x469dac8d…3411
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x6d6c8b37…a8cd
0x34b655…2a6f
6 touches
3 conflicts
0xab981df1…2941
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 0xb8185207a4…e36ccc
Audit this contract →
← previous block·next block →recent activity