← previous blocknext block →recent activity
Analyzing
Block #80,822,136
30 transactions · 23 stateful · 2026-06-12 15:30:34 UTC
Parallelism
80/100
Blocked
43%
Avg conflicts / tx
0.8
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #80,822,136 · 30 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
1w02w13w27w010w211w012w113w216w021w022w123w224w325w427w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xf0e8582d…e851
0x34b655…2a6f
6 touches
3 conflicts
0xfcdaee74…030e
0x34b655…2a6f
6 touches
3 conflicts
0x9e0e23b5…6910
0x34b655…2a6f
6 touches
3 conflicts
0xc38151f2…2bcb
0xc8689a…ee79
6 touches
3 conflicts
0x589dacfb…468b
0xd32edf…ff58
5 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x5581d709…ab77
0x2a68ba…90c5
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity