← previous blocknext block →recent activity
Analyzing
Block #107,278,134
35 transactions · 33 stateful · 2026-09-23 08:51:25 UTC
Parallelism
77/100
Blocked
64%
Avg conflicts / tx
1.71
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #107,278,134 · 35 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w616w325w626w634w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa9801e93…c0c4
0x34b655…2a6f
16 touches
28 conflicts
0x6bd4088b…62b9
0x34b655…2a6f
16 touches
28 conflicts
0x00000000…0013
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
14 touches
21 conflicts
0xd8d828a7…b64c
0x1b6862…e19c
14 touches
21 conflicts
0x99f91227…74a7
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…0012
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…001c
0x1b6862…e19c
12 touches
15 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 0xa9801e933c…c8c0c4
Audit this contract →
← previous block·next block →recent activity