← previous blocknext block →recent activity
Analyzing
Block #102,251,005
24 transactions · 24 stateful · 2026-09-05 18:04:05 UTC
Parallelism
79/100
Blocked
33%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,251,005 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w08w09w110w111w212w316w017w118w019w120w422w023w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb4c703ab…f8cf
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xe809324c…53d3
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x30c777f3…bacc
0x34b655…2a6f
4 touches
1 conflict
0x46fefcfe…366d
0x34b655…2a6f
4 touches
1 conflict
0x4ab70ccd…2683
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 0xb4c703ab76…fdf8cf
Audit this contract →
← previous block·next block →recent activity