← previous blocknext block →recent activity
Analyzing
Block #101,662,250
22 transactions · 20 stateful · 2026-09-03 16:28:28 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
1.14
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #101,662,250 · 22 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
1w02w13w04w15w07w08w19w110w214w015w316w417w520w521w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0x17d87f0d…bfc5
0x34b655…2a6f
8 touches
6 conflicts
0x62910921…3016
0x34b655…2a6f
6 touches
3 conflicts
0x52c55ca0…54ba
0x34b655…2a6f
4 touches
1 conflict
0x55863367…215c
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0x926971b8…7703
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
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity