← previous blocknext block →recent activity
Analyzing
Block #101,967,409
22 transactions · 21 stateful · 2026-09-04 18:06:39 UTC
Parallelism
77/100
Blocked
43%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,967,409 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w010w011w212w313w415w117w218w320w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x73194f11…8d9f
0x34b655…2a6f
6 touches
3 conflicts
0x94789504…4524
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xe057d58e…76fd
0xd32edf…ff58
5 touches
3 conflicts
0x35801c67…bcc0
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0000
0x24bf77…906e
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 0x73194f11f5…018d9f
Audit this contract →
← previous block·next block →recent activity