← previous blocknext block →recent activity
Analyzing
Block #107,841,549
31 transactions · 28 stateful · 2026-09-25 08:09:20 UTC
Parallelism
74/100
Blocked
71%
Avg conflicts / tx
1.9
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #107,841,549 · 31 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
1w02w13w24w35w46w57w68w09w112w213w414w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3256466c…790e
0x34b655…2a6f
16 touches
28 conflicts
0x508174fb…94d2
0x34b655…2a6f
16 touches
28 conflicts
0x00000000…0013
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
14 touches
21 conflicts
0x91945265…e592
0x1b6862…e19c
14 touches
21 conflicts
0xf7d8d036…828a
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…0012
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…001f
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 0x3256466c32…e1790e
Audit this contract →
← previous block·next block →recent activity