← previous blocknext block →recent activity
Analyzing
Block #106,930,644
32 transactions · 31 stateful · 2026-09-22 03:41:59 UTC
Parallelism
69/100
Blocked
48%
Avg conflicts / tx
1.31
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,930,644 · 32 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
1w02w03w16w07w18w29w310w411w312w513w614w715w816w926w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70986451…c6bd
0x34b655…2a6f
14 touches
21 conflicts
0x251ee419…4404
0x34b655…2a6f
12 touches
15 conflicts
0xccebf5c5…8758
0x34b655…2a6f
12 touches
15 conflicts
0xf6deafb5…5c25
0x34b655…2a6f
12 touches
15 conflicts
0x98783aa8…b36c
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe1c4e5ce…0de3
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
21 conflicts on slot 0x7098645134…3ac6bd
Audit this contract →
← previous block·next block →recent activity