← previous blocknext block →recent activity
Analyzing
Block #107,814,916
20 transactions · 20 stateful · 2026-09-25 05:55:18 UTC
Parallelism
35/100
Blocked
75%
Avg conflicts / tx
3.35
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #107,814,916 · 20 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w710w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x740fff9f…4244
0x34b655…2a6f
18 touches
36 conflicts
0xba5743c7…21c6
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0013
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0015
0x1b6862…e19c
16 touches
28 conflicts
0x7adcd8ca…db2e
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…0012
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…001f
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…002f
0x1b6862…e19c
14 touches
21 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
36 conflicts on slot 0x740fff9f9f…4a4244
Audit this contract →
← previous block·next block →recent activity