← previous blocknext block →recent activity
Analyzing
Block #107,806,600
34 transactions · 33 stateful · 2026-09-25 05:13:27 UTC
Parallelism
68/100
Blocked
58%
Avg conflicts / tx
1.82
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #107,806,600 · 34 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w08w19w410w211w012w520w521w622w724w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0x5a3732cb…edb3
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
12 touches
15 conflicts
0xdb428fe0…866d
0xd32edf…ff58
11 touches
15 conflicts
0x77ed432f…fa04
0x065c9d…c394
10 touches
10 conflicts
0xea02471d…1542
0x34b655…2a6f
10 touches
10 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
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity