← previous blocknext block →recent activity
Analyzing
Block #107,841,719
28 transactions · 25 stateful · 2026-09-25 08:10:12 UTC
Parallelism
68/100
Blocked
60%
Avg conflicts / tx
1.32
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #107,841,719 · 28 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w07w18w29w313w316w417w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x508174fb…94d2
0x34b655…2a6f
12 touches
15 conflicts
0x632c6987…ea7f
0xd32edf…ff58
9 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
6 touches
3 conflicts
0x17a7f697…dcb8
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x48c5fa5e…e4b7
0x34b655…2a6f
6 touches
3 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