← previous blocknext block →recent activity
Analyzing
Block #80,328,318
26 transactions · 23 stateful · 2026-06-10 08:37:40 UTC
Parallelism
77/100
Blocked
65%
Avg conflicts / tx
1.23
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #80,328,318 · 26 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
2w03w14w28w09w110w211w312w013w114w215w317w318w421w122w223w324w425w5
- 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
8 touches
6 conflicts
0x90f07a4f…d932
0x34b655…2a6f
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x217bd767…b79e
0x34b655…2a6f
6 touches
3 conflicts
0x379a09c4…259b
0x34b655…2a6f
4 touches
1 conflict
0x89ef0dba…31e2
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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