← previous blocknext block →recent activity
Analyzing
Block #101,151,261
18 transactions · 18 stateful · 2026-09-01 21:37:34 UTC
Parallelism
72/100
Blocked
22%
Avg conflicts / tx
0.28
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,151,261 · 18 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
6w011w115w216w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0xb75367ff…a2b7
0x34b655…2a6f
4 touches
1 conflict
0x53eac009…b61b
0x34b655…2a6f
4 touches
1 conflict
0xcfa1e92b…4b0c
0x34b655…2a6f
4 touches
1 conflict
0x8562996b…c9de
0x34b655…2a6f
2 touches
0 conflicts
0x9ad68d6f…bca7
0x34b655…2a6f
2 touches
0 conflicts
0xaae6463e…bfcc
0x34b655…2a6f
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity