← previous blocknext block →recent activity
Analyzing
Block #101,324,946
15 transactions · 15 stateful · 2026-09-02 12:11:23 UTC
Parallelism
53/100
Blocked
47%
Avg conflicts / tx
0.87
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #101,324,946 · 15 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
1w02w14w25w37w48w59w613w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6b48d6e…0705
0x34b655…2a6f
8 touches
6 conflicts
0xe8f5e33f…719c
0x34b655…2a6f
8 touches
6 conflicts
0xbdb7aec1…c95b
0x34b655…2a6f
8 touches
6 conflicts
0xddf15bfc…09c0
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x0490581d…adaf
0x34b655…2a6f
4 touches
1 conflict
0x1359fd46…5881
0x34b655…2a6f
4 touches
1 conflict
0x23769ebc…c8ed
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 0xa6b48d6e52…7c0705
Audit this contract →
← previous block·next block →recent activity