← previous blocknext block →recent activity
Analyzing
Block #80,642,227
33 transactions · 25 stateful · 2026-06-11 19:31:02 UTC
Parallelism
88/100
Blocked
32%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,642,227 · 33 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w07w18w212w315w118w019w128w029w130w231w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0xb18bf8…e9f3
8 touches
6 conflicts
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0xc38151f2…2bcb
0xc8689a…ee79
4 touches
1 conflict
0xa6017a9b…7cb6
0x065c9d…c394
2 touches
0 conflicts
0xb3519d8f…918d
0x065c9d…c394
2 touches
0 conflicts
0xeaa7a073…a16e
0x065c9d…c394
2 touches
0 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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity