← previous blocknext block →recent activity
Analyzing
Block #107,848,724
22 transactions · 21 stateful · 2026-09-25 08:45:27 UTC
Parallelism
64/100
Blocked
67%
Avg conflicts / tx
2.32
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #107,848,724 · 22 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
1w02w13w24w35w46w57w612w513w014w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xecff7c35…1b43
0x34b655…2a6f
16 touches
28 conflicts
0xbd6f7e54…ea76
0x34b655…2a6f
16 touches
28 conflicts
0xf30b9357…2e1e
0x34b655…2a6f
14 touches
21 conflicts
0x72083f0d…082a
0x34b655…2a6f
14 touches
21 conflicts
0x1f532139…dca7
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0x6aa624fd…a852
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0013
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 0xecff7c3510…111b43
Audit this contract →
← previous block·next block →recent activity