← previous blocknext block →recent activity
Analyzing
Block #101,151,548
26 transactions · 22 stateful · 2026-09-01 21:39:01 UTC
Parallelism
85/100
Blocked
32%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,151,548 · 26 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w112w013w114w215w016w318w119w225w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd9b50cd5…b4b1
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x30908823…a62d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x3f25409b…f92b
0x34b655…2a6f
4 touches
1 conflict
0x4e58f1d6…2fca
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
3 conflicts on slot 0xd9b50cd5e6…4eb4b1
Audit this contract →
← previous block·next block →recent activity