← previous blocknext block →recent activity
Analyzing
Block #80,237,713
13 transactions · 10 stateful · 2026-06-09 22:33:39 UTC
Parallelism
85/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,237,713 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
10w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x217bd767…b79e
0x34b655…2a6f
4 touches
1 conflict
0x84fb2a36…db89
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x71729695…12ca
0x1efe02…37d6
2 touches
0 conflicts
0x7a078850…cf6d
0x1efe02…37d6
2 touches
0 conflicts
0x9732ece9…5ed0
0x1efe02…37d6
2 touches
0 conflicts
0xc70d94b2…1e60
0x1efe02…37d6
2 touches
0 conflicts
0xd993ccf6…1392
0x1efe02…37d6
2 touches
0 conflicts
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
1 conflict on slot 0x217bd767aa…4fb79e
Audit this contract →
← previous block·next block →recent activity