← previous blocknext block →recent activity
Analyzing
Block #80,615,358
15 transactions · 12 stateful · 2026-06-11 16:31:38 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,615,358 · 15 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
1w02w13w212w013w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x326f2a00…a2a6
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x9d3f2124…725b
0x2a68ba…90c5
2 touches
1 conflict
0x3246eb65…c06e
0x065c9d…c394
2 touches
0 conflicts
0xa80ddb78…7294
0x065c9d…c394
2 touches
0 conflicts
0xb6ef9668…d853
0x065c9d…c394
2 touches
0 conflicts
0xcadd3e3d…4c15
0x065c9d…c394
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity