← previous blocknext block →recent activity
Analyzing
Block #107,989,245
16 transactions · 14 stateful · 2026-09-25 20:32:50 UTC
Parallelism
63/100
Blocked
43%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,989,245 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w37w48w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6ccaf360…188b
0x34b655…2a6f
12 touches
15 conflicts
0x11401e68…c822
0x34b655…2a6f
10 touches
10 conflicts
0x24c5620c…7ac5
0x34b655…2a6f
10 touches
10 conflicts
0x3d6c26e5…1b45
0x34b655…2a6f
10 touches
10 conflicts
0xb8dc136f…fb16
0xc8689a…ee79
10 touches
10 conflicts
0x84fe76b9…bd24
0x37db7f…ec7b
10 touches
10 conflicts
0xaf59c69d…c904
0x37db7f…ec7b
10 touches
10 conflicts
0xf99548c6…30b3
0x37db7f…ec7b
10 touches
10 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 0x6ccaf360e2…43188b
Audit this contract →
← previous block·next block →recent activity