← previous blocknext block →recent activity
Analyzing
Block #101,665,060
23 transactions · 20 stateful · 2026-09-03 16:42:36 UTC
Parallelism
65/100
Blocked
50%
Avg conflicts / tx
1.17
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #101,665,060 · 23 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w26w07w110w011w113w314w415w516w617w7
- 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
10 touches
10 conflicts
0xbb7e6651…ff5e
0x34b655…2a6f
6 touches
3 conflicts
0xc6615a36…3cf0
0x34b655…2a6f
6 touches
3 conflicts
0x7c4e558b…e4b6
0x34b655…2a6f
6 touches
3 conflicts
0x38c6ff01…689f
0x34b655…2a6f
6 touches
3 conflicts
0x3002a0e5…0d32
0x34b655…2a6f
6 touches
3 conflicts
0x375b6201…9c1e
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