← previous blocknext block →recent activity
Analyzing
Block #80,654,269
90 transactions · 9 stateful · 2026-06-11 20:51:20 UTC
Parallelism
98/100
Blocked
11%
Avg conflicts / tx
0.01
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,654,269 · 90 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
47w062w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe3471350…0bcf
0x34b655…2a6f
4 touches
1 conflict
0x60d07066…695c
0x34b655…2a6f
4 touches
1 conflict
0x90670859…26c7
0x34b655…2a6f
4 touches
1 conflict
0xf6476f21…3580
0x34b655…2a6f
4 touches
1 conflict
0xbbb9fa77…d121
0x34b655…2a6f
4 touches
1 conflict
0xd58b9a66…1c23
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x4b254c3a…b2f7
0x34b655…2a6f
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
1 conflict on slot 0xe347135026…5b0bcf
Audit this contract →
← previous block·next block →recent activity