← previous blocknext block →recent activity
Analyzing
Block #80,843,815
18 transactions · 16 stateful · 2026-06-12 17:55:16 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.83
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #80,843,815 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w16w112w213w314w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xffc2f21e…b393
0x34b655…2a6f
8 touches
6 conflicts
0x1ca68aab…5e4a
0x34b655…2a6f
6 touches
3 conflicts
0x0f3b22bf…e574
0x34b655…2a6f
4 touches
2 conflicts
0x727fbce7…0c80
0x34b655…2a6f
4 touches
1 conflict
0xde6b917f…3a72
0xa6afd3…d132
4 touches
1 conflict
0x1505a1cc…29fa
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
6 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity