← previous blocknext block →recent activity
Analyzing
Block #101,922,153
18 transactions · 17 stateful · 2026-09-04 14:16:59 UTC
Parallelism
61/100
Blocked
35%
Avg conflicts / tx
0.56
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #101,922,153 · 18 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
1w02w13w25w36w47w58w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53e08444…d671
0x34b655…2a6f
8 touches
6 conflicts
0x7c216fca…20cb
0x34b655…2a6f
8 touches
6 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
8 touches
6 conflicts
0x02372d42…1871
0x34b655…2a6f
8 touches
6 conflicts
0x999c658d…b185
0x34b655…2a6f
8 touches
6 conflicts
0xe8f860c0…35c9
0x34b655…2a6f
8 touches
6 conflicts
0xb826ef15…d248
0x34b655…2a6f
8 touches
6 conflicts
0xda09bbc9…b41b
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 0x53e0844469…6dd671
Audit this contract →
← previous block·next block →recent activity