← previous blocknext block →recent activity
Analyzing
Block #106,922,132
31 transactions · 30 stateful · 2026-09-22 02:59:08 UTC
Parallelism
58/100
Blocked
57%
Avg conflicts / tx
1.9
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #106,922,132 · 31 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w08w19w210w311w412w513w615w716w817w918w1019w1120w1229w230w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51087f5a…61f7
0x34b655…2a6f
16 touches
28 conflicts
0xecd87a39…d9c5
0x34b655…2a6f
14 touches
21 conflicts
0x93e4c736…3731
0x34b655…2a6f
14 touches
21 conflicts
0x42522e76…2592
0x34b655…2a6f
14 touches
21 conflicts
0x6cf9c605…7b8f
0x34b655…2a6f
12 touches
15 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
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
28 conflicts on slot 0x51087f5abf…f061f7
Audit this contract →
← previous block·next block →recent activity