← previous blocknext block →recent activity
Analyzing
Block #101,838,682
21 transactions · 21 stateful · 2026-09-04 07:15:53 UTC
Parallelism
71/100
Blocked
48%
Avg conflicts / tx
0.71
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,838,682 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w18w210w312w013w114w216w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8d616e7c…a6a1
0x34b655…2a6f
6 touches
3 conflicts
0x53e08444…d671
0x34b655…2a6f
6 touches
3 conflicts
0x67c1f465…38b3
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x02372d42…1871
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0xf36124ad…c08f
0x34b655…2a6f
6 touches
3 conflicts
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 0x8d616e7c6c…98a6a1
Audit this contract →
← previous block·next block →recent activity