← previous blocknext block →recent activity
Analyzing
Block #106,921,902
27 transactions · 25 stateful · 2026-09-22 02:57:58 UTC
Parallelism
63/100
Blocked
72%
Avg conflicts / tx
1.93
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,921,902 · 27 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w17w08w19w210w311w412w513w414w515w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x524f0872…0d12
0x34b655…2a6f
14 touches
21 conflicts
0x51087f5a…61f7
0x34b655…2a6f
12 touches
15 conflicts
0xa06430bf…57ce
0x34b655…2a6f
12 touches
15 conflicts
0x42522e76…2592
0x34b655…2a6f
12 touches
15 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
10 touches
10 conflicts
0x7cac1474…e8ec
0x34b655…2a6f
10 touches
10 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
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
21 conflicts on slot 0x524f087203…e70d12
Audit this contract →
← previous block·next block →recent activity