← previous blocknext block →recent activity
Analyzing
Block #101,673,792
23 transactions · 22 stateful · 2026-09-03 17:26:32 UTC
Parallelism
65/100
Blocked
50%
Avg conflicts / tx
1.09
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #101,673,792 · 23 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w19w010w111w212w313w414w515w216w619w722w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0x62910921…3016
0x34b655…2a6f
6 touches
3 conflicts
0xe3731239…e4cb
0x34b655…2a6f
6 touches
3 conflicts
0x53043411…237a
0x34b655…2a6f
4 touches
1 conflict
0x5a541bec…80fc
0x34b655…2a6f
4 touches
1 conflict
0x65bd465d…9770
0x34b655…2a6f
4 touches
1 conflict
0x85a88798…f85e
0x34b655…2a6f
4 touches
1 conflict
0x9a291a56…9a9c
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity