← previous blocknext block →recent activity
Analyzing
Block #80,165,267
25 transactions · 18 stateful · 2026-06-09 14:30:23 UTC
Parallelism
76/100
Blocked
39%
Avg conflicts / tx
0.68
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #80,165,267 · 25 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
1w02w111w016w120w121w222w323w424w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcdc1731c…b91a
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0x0382fe33…4c5f
0x34b655…2a6f
8 touches
6 conflicts
0xe03bbbf2…f240
0x34b655…2a6f
6 touches
3 conflicts
0x84fb2a36…db89
0x34b655…2a6f
6 touches
3 conflicts
0xfa324e43…889a
0x1b6862…e19c
4 touches
1 conflict
0x309ef367…e8a1
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 0xcdc1731c6b…b6b91a
Audit this contract →
← previous block·next block →recent activity