← previous blocknext block →recent activity
Analyzing
Block #80,138,692
20 transactions · 17 stateful · 2026-06-09 11:33:14 UTC
Parallelism
85/100
Blocked
24%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,138,692 · 20 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
1w02w13w24w05w113w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08cc68a2…2a59
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x487d2922…28b6
0x754704…b603
2 touches
1 conflict
0x86e6cece…1fd5
0x2a68ba…90c5
2 touches
1 conflict
0x5c8809d8…4de2
0x065c9d…c394
2 touches
0 conflicts
0xece16f24…6219
0x065c9d…c394
2 touches
0 conflicts
0xb3572c95…9c4a
0x2a68ba…90c5
2 touches
0 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
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 0x08cc68a2c8…482a59
Audit this contract →
← previous block·next block →recent activity