← previous blocknext block →recent activity
Analyzing
Block #107,816,587
30 transactions · 25 stateful · 2026-09-25 06:03:42 UTC
Parallelism
67/100
Blocked
56%
Avg conflicts / tx
1.63
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #107,816,587 · 30 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w19w011w212w213w314w415w516w117w618w719w820w921w122w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc7679110…572d
0x34b655…2a6f
16 touches
28 conflicts
0x49890ced…6f23
0x34b655…2a6f
12 touches
15 conflicts
0x42522e76…2592
0x34b655…2a6f
10 touches
10 conflicts
0x0b3f5b25…7d77
0x34b655…2a6f
8 touches
6 conflicts
0x08c1fec1…2246
0x34b655…2a6f
8 touches
6 conflicts
0x3750b746…5a9e
0x34b655…2a6f
6 touches
3 conflicts
0x2328941c…84d3
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
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
28 conflicts on slot 0xc7679110cf…22572d
Audit this contract →
← previous block·next block →recent activity