← previous blocknext block →recent activity
Analyzing
Block #101,302,122
18 transactions · 16 stateful · 2026-09-02 10:16:32 UTC
Parallelism
83/100
Blocked
25%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,302,122 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
0w01w02w13w04w110w217w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec1d6663…6042
0x34b655…2a6f
6 touches
3 conflicts
0x610f1b44…b654
0x34b655…2a6f
4 touches
1 conflict
0x078b16f2…f4ce
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
2 touches
0 conflicts
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 0xec1d6663f8…f86042
Audit this contract →
← previous block·next block →recent activity