← previous blocknext block →recent activity
Analyzing
Block #101,895,365
22 transactions · 21 stateful · 2026-09-04 12:01:15 UTC
Parallelism
68/100
Blocked
38%
Avg conflicts / tx
0.59
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #101,895,365 · 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
3w04w15w27w38w411w513w015w618w420w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf173eac8…b4ed
0x34b655…2a6f
8 touches
6 conflicts
0x898a08aa…c855
0x34b655…2a6f
6 touches
3 conflicts
0xaaf36ccb…f35c
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd4f6a526…ad10
0x34b655…2a6f
6 touches
3 conflicts
0xda50c9d5…674e
0x34b655…2a6f
6 touches
3 conflicts
0xe8114298…585b
0x34b655…2a6f
6 touches
3 conflicts
0xee109478…a9c1
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
6 conflicts on slot 0xf173eac816…86b4ed
Audit this contract →
← previous block·next block →recent activity