← previous blocknext block →recent activity
Analyzing
Block #106,216,882
32 transactions · 28 stateful · 2026-09-19 15:48:36 UTC
Parallelism
56/100
Blocked
68%
Avg conflicts / tx
2.09
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #106,216,882 · 32 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
1w02w13w04w15w17w18w29w310w411w512w613w714w815w919w1023w224w1125w1226w329w231w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf99856c4…370d
0x34b655…2a6f
18 touches
36 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xc389d1ff…6a00
0x34b655…2a6f
8 touches
6 conflicts
0xccf666d3…b805
0x34b655…2a6f
8 touches
6 conflicts
0x0b7a4c24…3857
0x34b655…2a6f
8 touches
6 conflicts
0xa242e227…2e45
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
36 conflicts on slot 0xf99856c491…9a370d
Audit this contract →
← previous block·next block →recent activity