← previous blocknext block →recent activity
Analyzing
Block #101,972,975
17 transactions · 16 stateful · 2026-09-04 18:34:47 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.41
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,972,975 · 17 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
1w02w15w06w111w215w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0xb652da8f…1216
0x754704…b603
4 touches
1 conflict
0xf96d61f8…8fd8
0x754704…b603
4 touches
1 conflict
0x6780777a…9fb1
0x99c7a7…8bf0
4 touches
1 conflict
0x75a77817…b0ed
0x99c7a7…8bf0
4 touches
1 conflict
0x3b096cfe…41e7
0x34b655…2a6f
4 touches
1 conflict
0x8e33015d…b134
0x34b655…2a6f
4 touches
1 conflict
0xa920abe6…6f3e
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 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity