← previous blocknext block →recent activity
Analyzing
Block #102,653,531
22 transactions · 19 stateful · 2026-09-07 04:03:01 UTC
Parallelism
82/100
Blocked
32%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,653,531 · 22 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
1w02w13w04w15w06w115w217w320w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xcf570cc1…b19c
0x99c7a7…8bf0
4 touches
1 conflict
0xce62e150…1e09
0x754704…b603
4 touches
1 conflict
0xa165a1e5…67be
0x754704…b603
4 touches
1 conflict
0x5f0647bd…59b9
0x754704…b603
4 touches
1 conflict
0xdb8288e3…7979
0x34b655…2a6f
4 touches
1 conflict
0x5ba932bd…1010
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity