← previous blocknext block →recent activity
Analyzing
Block #80,165,361
27 transactions · 20 stateful · 2026-06-09 14:31:00 UTC
Parallelism
81/100
Blocked
45%
Avg conflicts / tx
0.85
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,165,361 · 27 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w05w17w28w39w012w415w121w022w123w224w325w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x179fe783…6945
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x874f5c70…608f
0x34b655…2a6f
4 touches
1 conflict
0x908d4442…2c4b
0x34b655…2a6f
4 touches
1 conflict
0xa02e5cdd…76b8
0x34b655…2a6f
4 touches
1 conflict
0xa3b14322…657b
0x34b655…2a6f
4 touches
1 conflict
0xb8228d38…3953
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity