← previous blocknext block →recent activity
Analyzing
Block #106,052,720
17 transactions · 17 stateful · 2026-09-19 02:02:23 UTC
Parallelism
53/100
Blocked
65%
Avg conflicts / tx
2.06
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,052,720 · 17 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
1w02w13w04w25w37w38w49w110w112w513w514w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0fc536fb…1aa1
0x34b655…2a6f
16 touches
28 conflicts
0x773f594b…a1ea
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x94ded9f1…5774
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xd29e547b…a1dd
0x34b655…2a6f
8 touches
6 conflicts
0xbc09557f…5df2
0x34b655…2a6f
6 touches
3 conflicts
0x2d071de0…c86e
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
28 conflicts on slot 0x0fc536fb1f…c81aa1
Audit this contract →
← previous block·next block →recent activity