← previous blocknext block →recent activity
Analyzing
Block #80,234,581
28 transactions · 20 stateful · 2026-06-09 22:12:48 UTC
Parallelism
86/100
Blocked
35%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,234,581 · 28 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w010w016w117w119w020w122w123w224w225w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x25de453d…9573
0x34b655…2a6f
6 touches
3 conflicts
0xfe3d37ee…6e67
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0004
0x63e48b…53f2
4 touches
1 conflict
0x9a555477…19a8
0x754704…b603
4 touches
1 conflict
0x00000000…0003
0x63e48b…53f2
4 touches
1 conflict
0x00000000…0000
0x63e48b…53f2
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x7d42dc8b…fdb6
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
3 conflicts on slot 0x25de453d2d…559573
Audit this contract →
← previous block·next block →recent activity