← previous blocknext block →recent activity
Analyzing
Block #80,696,968
16 transactions · 14 stateful · 2026-06-12 01:35:52 UTC
Parallelism
63/100
Blocked
36%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #80,696,968 · 16 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
8w010w111w212w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x6fbc2e5a…e69c
0x34b655…2a6f
10 touches
10 conflicts
0x326a02b5…8dad
0x34b655…2a6f
10 touches
10 conflicts
0x170e4e4c…2b90
0x34b655…2a6f
9 touches
10 conflicts
0x0f2d78b1…7363
0x34b655…2a6f
6 touches
3 conflicts
0xe99ebc4d…22f9
0x34b655…2a6f
6 touches
3 conflicts
0xee9f03fd…1e57
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
15 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity