← previous blocknext block →recent activity
Analyzing
Block #102,231,316
26 transactions · 25 stateful · 2026-09-05 16:24:16 UTC
Parallelism
69/100
Blocked
56%
Avg conflicts / tx
1.5
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #102,231,316 · 26 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
1w03w14w15w26w311w112w215w116w218w319w422w523w624w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
16 touches
28 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
14 touches
21 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
8 touches
6 conflicts
0x045532dd…4b7d
0x34b655…2a6f
8 touches
6 conflicts
0xb9a0dde5…9e2b
0x34b655…2a6f
7 touches
6 conflicts
0x7c216fca…20cb
0x34b655…2a6f
6 touches
3 conflicts
0x7daf6443…fd36
0x34b655…2a6f
6 touches
3 conflicts
0x999c658d…b185
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 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity