← previous blocknext block →recent activity
Analyzing
Block #101,306,139
20 transactions · 19 stateful · 2026-09-02 10:36:45 UTC
Parallelism
75/100
Blocked
37%
Avg conflicts / tx
0.55
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,306,139 · 20 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
4w07w19w210w011w112w213w314w419w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb943a879…6e7f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x5e3014f0…b4e1
0x34b655…2a6f
6 touches
3 conflicts
0x6b595a5d…894c
0x34b655…2a6f
6 touches
3 conflicts
0x28eed2ad…c4b2
0x34b655…2a6f
4 touches
1 conflict
0x28eed2ad…c4b3
0x34b655…2a6f
4 touches
1 conflict
0x4a39a2a4…857b
0x34b655…2a6f
4 touches
1 conflict
0x502b3ee1…7f7c
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 0xb943a87918…f16e7f
Audit this contract →
← previous block·next block →recent activity