← previous blocknext block →recent activity
Analyzing
Block #107,838,939
24 transactions · 24 stateful · 2026-09-25 07:56:12 UTC
Parallelism
71/100
Blocked
54%
Avg conflicts / tx
1.33
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #107,838,939 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w08w39w010w111w212w313w414w515w616w122w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa2c4d203…05b6
0x34b655…2a6f
12 touches
15 conflicts
0x3b7b470e…2eae
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x961c0cd9…0937
0x34b655…2a6f
8 touches
6 conflicts
0xdbc6e634…e16c
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0xbbf62066…e101
0xd32edf…ff58
7 touches
6 conflicts
0x70335443…ff8e
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
15 conflicts on slot 0xa2c4d203df…b805b6
Audit this contract →
← previous block·next block →recent activity