← previous blocknext block →recent activity
Analyzing
Block #106,953,316
42 transactions · 39 stateful · 2026-09-22 05:36:06 UTC
Parallelism
60/100
Blocked
62%
Avg conflicts / tx
2.29
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #106,953,316 · 42 txs across 17 waves · depth 17
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w112w013w114w215w324w225w326w429w733w936w1137w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x67287ef9…2d07
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
12 touches
15 conflicts
0x6a14baa3…c6e9
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0x23769ebc…c8ed
0x34b655…2a6f
10 touches
10 conflicts
0xfa324e43…8899
0x1b6862…e19c
8 touches
6 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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity