← previous blocknext block →recent activity
Analyzing
Block #80,330,441
15 transactions · 11 stateful · 2026-06-10 08:51:47 UTC
Parallelism
87/100
Blocked
27%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,330,441 · 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
1w02w04w18w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x444c3ac5…2a12
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x3e8f1748…1d56
0x065c9d…c394
2 touches
0 conflicts
0x423e60ae…2531
0x065c9d…c394
2 touches
0 conflicts
0x57b9355a…e766
0x065c9d…c394
2 touches
0 conflicts
0x5a3f8550…f75a
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
1 conflict on slot 0x444c3ac5f5…6d2a12
Audit this contract →
← previous block·next block →recent activity