← previous blocknext block →recent activity
Analyzing
Block #80,990,706
11 transactions · 9 stateful · 2026-06-13 10:14:17 UTC
Parallelism
64/100
Blocked
33%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,990,706 · 11 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
2w08w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x0f2d78b1…7363
0x34b655…2a6f
6 touches
3 conflicts
0xc4ca986e…4e06
0x34b655…2a6f
6 touches
3 conflicts
0x76fc4c39…1659
0x34b655…2a6f
3 touches
1 conflict
0x81a7ba4d…8c4b
0x23c26b…7777
2 touches
0 conflicts
0x03622417…0bd6
0x2880ab…7b43
2 touches
0 conflicts
0x1d68c976…b6e6
0x34b655…2a6f
2 touches
0 conflicts
0x22874f53…8377
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity