← previous blocknext block →recent activity
Analyzing
Block #80,230,274
15 transactions · 13 stateful · 2026-06-09 21:43:50 UTC
Parallelism
87/100
Blocked
8%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,230,274 · 15 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
4w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x217bd767…b79e
0x34b655…2a6f
4 touches
1 conflict
0x97e2bfcd…fb19
0x34b655…2a6f
4 touches
1 conflict
0xf4e62e60…9f41
0x34b655…2a6f
4 touches
1 conflict
0x5f53a383…ac9b
0x1efe02…37d6
2 touches
0 conflicts
0xff5a8369…13eb
0x1efe02…37d6
2 touches
0 conflicts
0x1728ed63…499c
0xea1b8e…c5ec
2 touches
0 conflicts
0x3d7a5755…46ba
0xea1b8e…c5ec
2 touches
0 conflicts
0x455b104f…3960
0xea1b8e…c5ec
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