← previous blocknext block →recent activity
Analyzing
Block #106,216,727
27 transactions · 24 stateful · 2026-09-19 15:47:49 UTC
Parallelism
70/100
Blocked
50%
Avg conflicts / tx
1.15
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,216,727 · 27 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w210w112w313w416w117w518w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcdff6645…d9ba
0x34b655…2a6f
12 touches
15 conflicts
0x3d6151e6…0f88
0x34b655…2a6f
10 touches
10 conflicts
0x4118bd12…924a
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x159cff26…7665
0x34b655…2a6f
6 touches
3 conflicts
0x23a320fb…cbd7
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
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
15 conflicts on slot 0xcdff664583…f7d9ba
Audit this contract →
← previous block·next block →recent activity