← previous blocknext block →recent activity
Analyzing
Block #107,816,186
23 transactions · 22 stateful · 2026-09-25 06:01:41 UTC
Parallelism
70/100
Blocked
64%
Avg conflicts / tx
1.7
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #107,816,186 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w38w410w011w112w213w314w415w516w617w122w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbdd97c21…e3d0
0x34b655…2a6f
14 touches
21 conflicts
0xe098738f…9bbe
0x34b655…2a6f
12 touches
15 conflicts
0x72083f0d…082a
0x34b655…2a6f
12 touches
15 conflicts
0xb1616aa9…771c
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x4e7eb462…b2b1
0x1b6862…e19c
10 touches
10 conflicts
0x5a4e3296…d501
0xd32edf…ff58
9 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
21 conflicts on slot 0xbdd97c213f…cee3d0
Audit this contract →
← previous block·next block →recent activity