← previous blocknext block →recent activity
Analyzing
Block #80,253,273
29 transactions · 24 stateful · 2026-06-10 00:17:19 UTC
Parallelism
90/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,253,273 · 29 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w17w08w09w110w211w012w116w017w223w024w126w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb8228d38…3953
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x217bd767…b79e
0x34b655…2a6f
6 touches
3 conflicts
0x80afd9d9…57cf
0x065c9d…c394
6 touches
3 conflicts
0x070a562a…8147
0x34b655…2a6f
4 touches
1 conflict
0x0df3b1db…727b
0x34b655…2a6f
4 touches
1 conflict
0x0eac6378…36f4
0x34b655…2a6f
4 touches
1 conflict
0x4f412a3d…b1f7
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
3 conflicts on slot 0xb8228d3887…e23953
Audit this contract →
← previous block·next block →recent activity