← previous blocknext block →recent activity
Analyzing
Block #101,660,830
22 transactions · 21 stateful · 2026-09-03 16:21:19 UTC
Parallelism
73/100
Blocked
57%
Avg conflicts / tx
1.09
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,660,830 · 22 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
1w02w13w14w15w26w37w410w211w313w014w115w418w520w021w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x375b6201…9c1e
0x34b655…2a6f
8 touches
6 conflicts
0xf36124ad…c08f
0x34b655…2a6f
6 touches
3 conflicts
0xfd713bab…a651
0x34b655…2a6f
6 touches
3 conflicts
0xfd791576…6717
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0x67c1f465…38b3
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
10 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity