← previous blocknext block →recent activity
Analyzing
Block #107,442,019
20 transactions · 20 stateful · 2026-09-23 22:36:21 UTC
Parallelism
70/100
Blocked
50%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,442,019 · 20 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
1w02w13w26w27w38w49w510w311w012w114w018w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a35acfb…d1b1
0x37db7f…ec7b
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0x8a35acfb…d1b0
0x37db7f…ec7b
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x3643741b…109c
0x34b655…2a6f
6 touches
3 conflicts
0xba5743c7…21c6
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x80e4a768…096c
0xd32edf…ff58
5 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: 0x37db7fbf…3eec7b
15 conflicts on slot 0x8a35acfbc1…6bd1b1
Audit this contract →
← previous block·next block →recent activity