← previous blocknext block →recent activity
Analyzing
Block #80,328,376
25 transactions · 21 stateful · 2026-06-10 08:38:03 UTC
Parallelism
80/100
Blocked
43%
Avg conflicts / tx
0.84
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,328,376 · 25 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
2w04w05w16w27w38w411w120w021w122w223w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xc38151f2…2bcb
0xc8689a…ee79
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x62d6e82b…a750
0x34b655…2a6f
4 touches
1 conflict
0x6659466a…5090
0x34b655…2a6f
4 touches
1 conflict
0x833ebd97…5abb
0x34b655…2a6f
4 touches
1 conflict
0x8c09fdbf…2abc
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity