← previous blocknext block →recent activity
Analyzing
Block #80,168,137
49 transactions · 39 stateful · 2026-06-09 14:49:32 UTC
Parallelism
65/100
Blocked
72%
Avg conflicts / tx
2.49
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #80,168,137 · 49 txs across 17 waves · depth 17
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w111w012w013w114w215w316w417w518w619w720w833w934w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0x90f07a4f…d932
0x34b655…2a6f
16 touches
28 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
16 touches
28 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0x88c56519…b0e8
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x179fe783…6945
0xa6afd3…d132
10 touches
10 conflicts
0x8cf3d245…1d0d
0x69df8a…6292
8 touches
6 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
36 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity