← previous blocknext block →recent activity
Analyzing
Block #101,088,523
18 transactions · 17 stateful · 2026-09-01 16:21:58 UTC
Parallelism
61/100
Blocked
41%
Avg conflicts / tx
0.72
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #101,088,523 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w27w310w411w512w617w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2de1aea…8024
0x34b655…2a6f
6 touches
3 conflicts
0xc95f91db…a901
0x34b655…2a6f
6 touches
3 conflicts
0x9a786711…5b52
0x34b655…2a6f
6 touches
3 conflicts
0x63a8652c…5b43
0x34b655…2a6f
4 touches
1 conflict
0x63a8652c…5b44
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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 0xe2de1aeae5…be8024
Audit this contract →
← previous block·next block →recent activity