← previous blocknext block →recent activity
Analyzing
Block #102,243,424
24 transactions · 23 stateful · 2026-09-05 17:25:43 UTC
Parallelism
83/100
Blocked
35%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,243,424 · 24 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
1w02w13w04w15w26w39w015w016w119w121w022w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcd7574f…a3a2
0x34b655…2a6f
8 touches
6 conflicts
0x9c088939…ddd7
0x34b655…2a6f
8 touches
6 conflicts
0x9d7ac3b9…22f8
0x34b655…2a6f
8 touches
6 conflicts
0xa7e3ddfa…f0c7
0x34b655…2a6f
8 touches
6 conflicts
0xe0da07e4…ccf2
0x34b655…2a6f
8 touches
6 conflicts
0xfa805f95…72a4
0x34b655…2a6f
8 touches
6 conflicts
0x2014bf1d…d13f
0x34b655…2a6f
8 touches
6 conflicts
0x30c777f3…bacc
0x34b655…2a6f
8 touches
6 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 0xfcd7574f97…54a3a2
Audit this contract →
← previous block·next block →recent activity