← previous blocknext block →recent activity
Analyzing
Block #106,934,389
19 transactions · 18 stateful · 2026-09-22 04:00:49 UTC
Parallelism
68/100
Blocked
33%
Avg conflicts / tx
0.68
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,934,389 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
9w010w011w112w214w215w316w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf7b76d2f…1b9c
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xe7eb4e21…4345
0x34b655…2a6f
6 touches
3 conflicts
0xd1b40f29…9b9d
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xab981df1…2941
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
4 touches
1 conflict
0x6a9340ab…27b4
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0xf7b76d2f54…f41b9c
Audit this contract →
← previous block·next block →recent activity