← previous blocknext block →recent activity
Analyzing
Block #80,771,399
13 transactions · 13 stateful · 2026-06-12 09:52:17 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,771,399 · 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
4w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba9f88e8…9c33
0x34b655…2a6f
4 touches
1 conflict
0x1b5d2e60…99b5
0x34b655…2a6f
4 touches
1 conflict
0xf6476f21…3580
0x34b655…2a6f
4 touches
1 conflict
0x00ddbbf2…4588
0x34b655…2a6f
4 touches
1 conflict
0x73d70be1…c3d1
0x34b655…2a6f
4 touches
1 conflict
0x925e20a2…36a8
0x34b655…2a6f
4 touches
1 conflict
0x98bd7b25…3338
0x34b655…2a6f
4 touches
1 conflict
0x5aa29d18…83c7
0x34b655…2a6f
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 0xba9f88e88a…879c33
Audit this contract →
← previous block·next block →recent activity