← previous blocknext block →recent activity
Analyzing
Block #106,923,836
38 transactions · 33 stateful · 2026-09-22 03:07:43 UTC
Parallelism
60/100
Blocked
67%
Avg conflicts / tx
2
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #106,923,836 · 38 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w28w09w110w213w014w115w216w317w418w519w620w721w822w923w1024w1125w1226w1327w1432w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc8c615d4…5da3
0x34b655…2a6f
20 touches
45 conflicts
0x81696049…331c
0x34b655…2a6f
18 touches
36 conflicts
0x42522e76…2592
0x34b655…2a6f
18 touches
36 conflicts
0x8590b692…b267
0x34b655…2a6f
14 touches
21 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
12 touches
15 conflicts
0x681b1d0d…2e6b
0x34b655…2a6f
12 touches
15 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xd98b3c10…67b8
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
45 conflicts on slot 0xc8c615d41e…025da3
Audit this contract →
← previous block·next block →recent activity