← previous blocknext block →recent activity
Analyzing
Block #101,501,303
19 transactions · 15 stateful · 2026-09-03 02:58:48 UTC
Parallelism
74/100
Blocked
53%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,501,303 · 19 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
1w02w13w24w25w36w410w011w114w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8bf661cb…bcd2
0x34b655…2a6f
8 touches
6 conflicts
0x65f011a5…bc6e
0x34b655…2a6f
8 touches
6 conflicts
0x32e1d03e…68a7
0x34b655…2a6f
6 touches
3 conflicts
0xfa805f95…72a4
0x34b655…2a6f
6 touches
3 conflicts
0xc02616f8…cd49
0x34b655…2a6f
6 touches
3 conflicts
0xa735de1d…29b0
0x34b655…2a6f
6 touches
3 conflicts
0x3b3ba543…c977
0xd32edf…ff58
5 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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 0x8bf661cb38…d4bcd2
Audit this contract →
← previous block·next block →recent activity