← previous blocknext block →recent activity
Analyzing
Block #107,841,714
34 transactions · 28 stateful · 2026-09-25 08:10:10 UTC
Parallelism
71/100
Blocked
61%
Avg conflicts / tx
1.29
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #107,841,714 · 34 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w38w09w113w214w315w416w518w619w729w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x508174fb…94d2
0x34b655…2a6f
12 touches
15 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001f
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002f
0x1b6862…e19c
8 touches
6 conflicts
0xac79a0c7…be16
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
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
15 conflicts on slot 0x508174fbc3…8094d2
Audit this contract →
← previous block·next block →recent activity