← previous blocknext block →recent activity
Analyzing
Block #102,191,707
19 transactions · 18 stateful · 2026-09-05 13:03:39 UTC
Parallelism
58/100
Blocked
44%
Avg conflicts / tx
1.53
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #102,191,707 · 19 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w212w013w114w315w416w517w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0x80afb36e…239c
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xb0a7d979…59ac
0x34b655…2a6f
7 touches
6 conflicts
0xa1324748…2f92
0x34b655…2a6f
6 touches
3 conflicts
0xc852b267…9d14
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity