← previous blocknext block →recent activity
Analyzing
Block #106,931,188
33 transactions · 33 stateful · 2026-09-22 03:44:43 UTC
Parallelism
58/100
Blocked
64%
Avg conflicts / tx
2.61
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #106,931,188 · 33 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w08w19w210w311w412w513w615w116w717w818w919w1020w1121w1224w1326w131w332w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c26d635…1bbf
0x34b655…2a6f
18 touches
36 conflicts
0xfaf89f45…ced6
0x34b655…2a6f
18 touches
36 conflicts
0x3273cbc8…b4c8
0x34b655…2a6f
14 touches
21 conflicts
0x49890ced…6f23
0x34b655…2a6f
14 touches
21 conflicts
0x48f91335…a89c
0x34b655…2a6f
14 touches
21 conflicts
0xccebf5c5…8758
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x51087f5a…61f7
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
36 conflicts on slot 0x6c26d63540…461bbf
Audit this contract →
← previous block·next block →recent activity