← previous blocknext block →recent activity
Analyzing
Block #106,916,511
32 transactions · 31 stateful · 2026-09-22 02:30:50 UTC
Parallelism
50/100
Blocked
61%
Avg conflicts / tx
2.41
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #106,916,511 · 32 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w16w07w18w09w110w211w312w413w514w615w716w817w918w1019w1120w1221w1322w1423w1524w228w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53ca1284…cb2c
0x34b655…2a6f
20 touches
45 conflicts
0xf782ee27…41cd
0x34b655…2a6f
18 touches
36 conflicts
0xccebf5c5…8758
0x34b655…2a6f
18 touches
36 conflicts
0x51087f5a…61f7
0x34b655…2a6f
16 touches
28 conflicts
0x803d32b5…8094
0x34b655…2a6f
14 touches
21 conflicts
0x49890ced…6f23
0x34b655…2a6f
14 touches
21 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
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
45 conflicts on slot 0x53ca128412…cacb2c
Audit this contract →
← previous block·next block →recent activity