← previous blocknext block →recent activity
Analyzing
Block #80,833,491
31 transactions · 26 stateful · 2026-06-12 16:46:20 UTC
Parallelism
87/100
Blocked
38%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,833,491 · 31 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
1w02w03w04w15w27w18w09w110w213w014w115w216w320w022w324w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xde6b917f…3a72
0xa6afd3…d132
8 touches
6 conflicts
0x90f07a4f…d932
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xb0e9898d…42c2
0xa6afd3…d132
8 touches
6 conflicts
0xb4e9858d…4080
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x4f4bdabd…ffba
0x34b655…2a6f
6 touches
3 conflicts
0x40970e69…da50
0x69df8a…6292
6 touches
3 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: 0xa6afd386…b0d132
6 conflicts on slot 0xde6b917faa…a83a72
Audit this contract →
← previous block·next block →recent activity