← previous blocknext block →recent activity
Analyzing
Block #107,816,439
19 transactions · 18 stateful · 2026-09-25 06:02:57 UTC
Parallelism
63/100
Blocked
56%
Avg conflicts / tx
1.47
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #107,816,439 · 19 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
1w02w13w24w39w010w111w212w313w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbdd97c21…e3d0
0x34b655…2a6f
14 touches
21 conflicts
0xaa97569b…1480
0x34b655…2a6f
14 touches
21 conflicts
0xe098738f…9bbe
0x34b655…2a6f
10 touches
10 conflicts
0xc10b903d…2f54
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…002f
0x1b6862…e19c
8 touches
6 conflicts
0xd1480c90…ae0b
0x1b6862…e19c
8 touches
6 conflicts
0xb6039eff…b0d1
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 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
21 conflicts on slot 0xbdd97c213f…cee3d0
Audit this contract →
← previous block·next block →recent activity