← previous blocknext block →recent activity
Analyzing
Block #101,852,420
13 transactions · 13 stateful · 2026-09-04 08:25:00 UTC
Parallelism
77/100
Blocked
31%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,852,420 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w29w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x67c1f465…38b3
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0x0ec07cf7…c0c9
0x34b655…2a6f
6 touches
3 conflicts
0x9bff3222…a246
0x34b655…2a6f
6 touches
3 conflicts
0x9c088939…ddd7
0x34b655…2a6f
6 touches
3 conflicts
0xc52785b9…08f8
0x34b655…2a6f
6 touches
3 conflicts
0xd4f6a526…ad10
0x34b655…2a6f
6 touches
3 conflicts
0xf36124ad…c08f
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
3 conflicts on slot 0x67c1f46537…4d38b3
Audit this contract →
← previous block·next block →recent activity