← previous blocknext block →recent activity
Analyzing
Block #101,491,269
22 transactions · 20 stateful · 2026-09-03 02:08:19 UTC
Parallelism
68/100
Blocked
45%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #101,491,269 · 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
1w02w13w210w111w012w114w217w018w319w420w521w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
8 touches
6 conflicts
0x58c745f6…fe5d
0x34b655…2a6f
6 touches
3 conflicts
0xb653282d…8e3a
0x34b655…2a6f
6 touches
3 conflicts
0x6cda5bc9…8e0e
0x34b655…2a6f
4 touches
1 conflict
0x761d0236…2ffe
0x34b655…2a6f
4 touches
1 conflict
0x79ec4509…1f61
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
10 conflicts on slot 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity