← previous blocknext block →recent activity
Analyzing
Block #80,693,950
18 transactions · 16 stateful · 2026-06-12 01:15:48 UTC
Parallelism
50/100
Blocked
56%
Avg conflicts / tx
1.78
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #80,693,950 · 18 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w110w111w212w313w414w515w616w717w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x326a02b5…8dad
0x34b655…2a6f
8 touches
6 conflicts
0x6fbc2e5a…e69c
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x73d70be1…c3d1
0x34b655…2a6f
6 touches
3 conflicts
0x7d02a2c5…9802
0x34b655…2a6f
6 touches
3 conflicts
0x6f9752ff…3ec8
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
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity