← previous blocknext block →recent activity
Analyzing
Block #80,833,624
26 transactions · 15 stateful · 2026-06-12 16:47:14 UTC
Parallelism
81/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,833,624 · 26 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
2w03w19w013w116w223w024w325w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07a0dea2…ca8c
0x34b655…2a6f
10 touches
10 conflicts
0x548145a9…cfce
0x34b655…2a6f
6 touches
3 conflicts
0xf6476f21…3580
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x37b10c3b…8fcf
0x34b655…2a6f
6 touches
3 conflicts
0x396415f7…4a70
0x34b655…2a6f
4 touches
1 conflict
0x6fbc2e5a…e69c
0x34b655…2a6f
4 touches
1 conflict
0x86977b3d…a9c4
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 0x07a0dea248…11ca8c
Audit this contract →
← previous block·next block →recent activity