← previous blocknext block →recent activity
Analyzing
Block #101,300,629
24 transactions · 18 stateful · 2026-09-02 10:09:02 UTC
Parallelism
88/100
Blocked
28%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,300,629 · 24 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w012w013w117w118w220w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x86bd79a5…1f48
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xf9e48d0a…6baa
0x34b655…2a6f
6 touches
3 conflicts
0xcb45d9d6…cb84
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x422d5490…52d9
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4e135144…4167
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 0x86bd79a5a6…961f48
Audit this contract →
← previous block·next block →recent activity