← previous blocknext block →recent activity
Analyzing
Block #80,754,766
111 transactions · 17 stateful · 2026-06-12 08:01:20 UTC
Parallelism
95/100
Blocked
41%
Avg conflicts / tx
0.17
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #80,754,766 · 111 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
1w02w110w031w150w266w381w494w5109w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf6476f21…3580
0x34b655…2a6f
12 touches
15 conflicts
0x0f2d78b1…7363
0x34b655…2a6f
8 touches
6 conflicts
0x548145a9…cfce
0x34b655…2a6f
8 touches
6 conflicts
0x37b10c3b…8fcf
0x34b655…2a6f
8 touches
6 conflicts
0x1eb0fab5…3517
0x34b655…2a6f
6 touches
3 conflicts
0x06726618…fafd
0x34b655…2a6f
5 touches
4 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x0c6e2941…9d10
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
15 conflicts on slot 0xf6476f21e7…f83580
Audit this contract →
← previous block·next block →recent activity