← previous blocknext block →recent activity
Analyzing
Block #101,971,019
21 transactions · 17 stateful · 2026-09-04 18:24:54 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
1.29
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #101,971,019 · 21 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
1w03w07w111w012w114w115w016w217w318w419w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xddd20e39…d524
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0xf3d10975…0d07
0x34b655…2a6f
10 touches
10 conflicts
0xe5e7089a…fb91
0x34b655…2a6f
10 touches
10 conflicts
0x309ef367…e8a1
0x34b655…2a6f
6 touches
3 conflicts
0x5ffc25fa…b119
0x34b655…2a6f
5 touches
3 conflicts
0xc4c059d8…185d
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 0xddd20e3989…a2d524
Audit this contract →
← previous block·next block →recent activity