← previous blocknext block →recent activity
Analyzing
Block #107,440,630
18 transactions · 17 stateful · 2026-09-23 22:29:21 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,440,630 · 18 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
3w06w07w18w29w310w411w515w416w517w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x88cf2d31…3d64
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x12662ad4…c4d2
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 conflicts
0xcb45d9d6…cb87
0x1b6862…e19c
6 touches
3 conflicts
0x6931c9a0…d891
0xd32edf…ff58
5 touches
3 conflicts
0x8d175439…fb79
0x34b655…2a6f
4 touches
1 conflict
0x8f63f383…6eda
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
10 conflicts on slot 0x88cf2d3101…3b3d64
Audit this contract →
← previous block·next block →recent activity