← previous blocknext block →recent activity
Analyzing
Block #101,300,917
27 transactions · 24 stateful · 2026-09-02 10:10:29 UTC
Parallelism
81/100
Blocked
29%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,300,917 · 27 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
3w04w16w010w111w012w113w220w224w326w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf48fa71e…bb52
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xeb5b61a2…b2bc
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x5da59c2b…d7b2
0x34b655…2a6f
6 touches
3 conflicts
0xfcc8f826…7c5f
0x34b655…2a6f
4 touches
1 conflict
0x16959359…a041
0x34b655…2a6f
4 touches
1 conflict
0x3f12324f…3c43
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
6 conflicts on slot 0xf48fa71eee…43bb52
Audit this contract →
← previous block·next block →recent activity