← previous blocknext block →recent activity
Analyzing
Block #101,502,769
24 transactions · 21 stateful · 2026-09-03 03:06:11 UTC
Parallelism
75/100
Blocked
52%
Avg conflicts / tx
1.04
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,502,769 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w08w19w210w011w114w415w016w317w419w520w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3dc5798b…5c87
0x34b655…2a6f
10 touches
10 conflicts
0x6fc62003…278e
0xd32edf…ff58
9 touches
10 conflicts
0xd2a76d80…ee44
0x34b655…2a6f
6 touches
3 conflicts
0x4f858307…7642
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x86a58238…7077
0x34b655…2a6f
4 touches
1 conflict
0x90a021f0…f922
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
10 conflicts on slot 0x3dc5798bb7…f95c87
Audit this contract →
← previous block·next block →recent activity