← previous blocknext block →recent activity
Analyzing
Block #101,853,429
14 transactions · 13 stateful · 2026-09-04 08:30:04 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,853,429 · 14 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
1w02w13w05w06w111w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x110a3804…f842
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xde1daa69…719a
0x34b655…2a6f
6 touches
3 conflicts
0x2203331a…b430
0x34b655…2a6f
4 touches
1 conflict
0x3765e35e…1cb4
0x34b655…2a6f
4 touches
1 conflict
0x3f26c5cf…6227
0x34b655…2a6f
4 touches
1 conflict
0x4cc1bee3…a654
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity