← previous blocknext block →recent activity
Analyzing
Block #107,814,367
18 transactions · 17 stateful · 2026-09-25 05:52:32 UTC
Parallelism
72/100
Blocked
53%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,814,367 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w38w39w010w111w212w313w416w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaa645624…7ea9
0x34b655…2a6f
10 touches
10 conflicts
0xba522812…1f1f
0x34b655…2a6f
10 touches
10 conflicts
0xcc844ab5…4c6d
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0xba5743c7…21c6
0x1b6862…e19c
8 touches
6 conflicts
0x3a92e9ba…a8c8
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
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
10 conflicts on slot 0xaa64562485…c67ea9
Audit this contract →
← previous block·next block →recent activity