← previous blocknext block →recent activity
Analyzing
Block #107,817,083
21 transactions · 21 stateful · 2026-09-25 06:06:12 UTC
Parallelism
67/100
Blocked
52%
Avg conflicts / tx
1.57
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #107,817,083 · 21 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
1w02w13w24w39w010w111w212w313w414w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5cf4d55d…c588
0x34b655…2a6f
14 touches
21 conflicts
0xe6341958…a301
0x34b655…2a6f
12 touches
15 conflicts
0x69ee34d1…30f8
0x34b655…2a6f
10 touches
10 conflicts
0x6b1259e6…4e14
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xbc2a01c9…7b62
0xd32edf…ff58
7 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 0x5cf4d55d39…13c588
Audit this contract →
← previous block·next block →recent activity