← previous blocknext block →recent activity
Analyzing
Block #106,917,338
24 transactions · 23 stateful · 2026-09-22 02:35:00 UTC
Parallelism
63/100
Blocked
70%
Avg conflicts / tx
2.33
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,917,338 · 24 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w16w07w18w29w310w411w512w213w314w415w516w617w718w819w621w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70986451…c6bd
0x34b655…2a6f
16 touches
28 conflicts
0x251ee419…4404
0x34b655…2a6f
14 touches
21 conflicts
0xccebf5c5…8758
0x34b655…2a6f
14 touches
21 conflicts
0x6c60fbcf…8744
0x34b655…2a6f
14 touches
21 conflicts
0xc7ce92b1…25d0
0x34b655…2a6f
12 touches
15 conflicts
0x49890ced…6f23
0x34b655…2a6f
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x05f274af…9206
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
28 conflicts on slot 0x7098645134…3ac6bd
Audit this contract →
← previous block·next block →recent activity