← previous blocknext block →recent activity
Analyzing
Block #80,164,163
24 transactions · 18 stateful · 2026-06-09 14:23:01 UTC
Parallelism
79/100
Blocked
44%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,164,163 · 24 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
1w02w14w15w06w013w214w118w120w221w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xd1e4de02…07e9
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x2b5cb9f0…1d10
0x34b655…2a6f
6 touches
3 conflicts
0x65bb8d8c…8bb0
0x34b655…2a6f
6 touches
3 conflicts
0xb0e4f69d…34e7
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
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 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity