← previous blocknext block →recent activity
Analyzing
Block #101,659,563
30 transactions · 24 stateful · 2026-09-03 16:14:57 UTC
Parallelism
83/100
Blocked
38%
Avg conflicts / tx
0.37
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,659,563 · 30 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
2w03w17w09w112w013w114w216w217w322w224w427w028w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x024b482b…16b0
0x34b655…2a6f
6 touches
3 conflicts
0x1a2e73cf…5ff5
0x34b655…2a6f
6 touches
3 conflicts
0x65f011a5…bc6e
0x34b655…2a6f
6 touches
3 conflicts
0x67c1f465…38b3
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0xa735de1d…29b0
0x34b655…2a6f
6 touches
3 conflicts
0xc6ce40ba…9b56
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0002
0x659bd0…a9da
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 0x024b482b0a…2616b0
Audit this contract →
← previous block·next block →recent activity