← previous blocknext block →recent activity
Analyzing
Block #107,839,238
33 transactions · 27 stateful · 2026-09-25 07:57:42 UTC
Parallelism
88/100
Blocked
37%
Avg conflicts / tx
0.61
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #107,839,238 · 33 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w38w112w113w214w215w316w017w031w132w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xef3f5637…f47c
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0xe073e79e…b9e8
0x34b655…2a6f
8 touches
6 conflicts
0x91220b8f…7a08
0x1b6862…e19c
8 touches
6 conflicts
0xcba473e0…1201
0xd32edf…ff58
7 touches
6 conflicts
0xe098738f…9bbe
0x34b655…2a6f
6 touches
3 conflicts
0xdcd07321…1c31
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
6 conflicts on slot 0xef3f5637ee…e7f47c
Audit this contract →
← previous block·next block →recent activity