← previous blocknext block →recent activity
Analyzing
Block #107,815,392
21 transactions · 18 stateful · 2026-09-25 05:57:41 UTC
Parallelism
81/100
Blocked
56%
Avg conflicts / tx
0.81
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #107,815,392 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w19w010w112w213w014w115w016w217w318w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2328941c…84d3
0x34b655…2a6f
8 touches
6 conflicts
0xd0f6f4f2…dffa
0x34b655…2a6f
8 touches
6 conflicts
0x2a880840…7365
0x34b655…2a6f
8 touches
6 conflicts
0xc7679110…572d
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xbd8e15f1…c466
0xd32edf…ff58
5 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
6 conflicts on slot 0x2328941c9c…fc84d3
Audit this contract →
← previous block·next block →recent activity