← previous blocknext block →recent activity
Analyzing
Block #101,799,404
15 transactions · 13 stateful · 2026-09-04 03:58:20 UTC
Parallelism
60/100
Blocked
46%
Avg conflicts / tx
0.8
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,799,404 · 15 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w111w212w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1c4e5ce…0dec
0x34b655…2a6f
8 touches
6 conflicts
0xbc8fb280…76a3
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xbd590df7…9891
0x34b655…2a6f
6 touches
3 conflicts
0xb0f5d668…99ac
0x34b655…2a6f
6 touches
3 conflicts
0x64b7d292…67c9
0x34b655…2a6f
4 touches
1 conflict
0xdfb072fd…e101
0x34b655…2a6f
4 touches
1 conflict
0xc4888af6…26b5
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
6 conflicts on slot 0xe1c4e5ce15…770dec
Audit this contract →
← previous block·next block →recent activity