← previous blocknext block →recent activity
Analyzing
Block #80,703,795
19 transactions · 16 stateful · 2026-06-12 02:21:22 UTC
Parallelism
74/100
Blocked
31%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,703,795 · 19 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
3w06w113w014w115w216w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x0f2d78b1…7363
0x34b655…2a6f
8 touches
6 conflicts
0xa4658f5c…b257
0x34b655…2a6f
6 touches
3 conflicts
0xe9991812…e391
0x34b655…2a6f
6 touches
3 conflicts
0xfa1a8731…ca65
0x34b655…2a6f
6 touches
3 conflicts
0x5ec9f739…2305
0x34b655…2a6f
4 touches
1 conflict
0x67f87cdf…e5b6
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity