← previous blocknext block →recent activity
Analyzing
Block #102,816,757
22 transactions · 18 stateful · 2026-09-07 17:47:26 UTC
Parallelism
73/100
Blocked
44%
Avg conflicts / tx
0.64
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,816,757 · 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
1w02w13w27w315w016w117w418w419w120w021w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcd5e68f…2a12
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
6 touches
3 conflicts
0x5e3a594a…2471
0x34b655…2a6f
6 touches
3 conflicts
0x6940ae48…0c29
0x34b655…2a6f
6 touches
3 conflicts
0xeb5aa77a…c2ad
0xd32edf…ff58
5 touches
3 conflicts
0xfac61869…a55e
0x1b6862…e19c
4 touches
1 conflict
0x21e79ad8…c5db
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 0xfcd5e68f28…382a12
Audit this contract →
← previous block·next block →recent activity