← previous blocknext block →recent activity
Analyzing
Block #80,825,777
22 transactions · 15 stateful · 2026-06-12 15:54:48 UTC
Parallelism
91/100
Blocked
27%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,825,777 · 22 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
2w04w19w012w113w014w120w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x217bd767…b79e
0x34b655…2a6f
4 touches
1 conflict
0x9a291a56…9a9c
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xc38151f2…2bcb
0xc8689a…ee79
4 touches
1 conflict
0x66a1faa8…66ed
0x065c9d…c394
3 touches
1 conflict
0x86d4b68b…d2d6
0x065c9d…c394
3 touches
1 conflict
0x1bd4950c…2445
0x0a3323…0a3c
2 touches
0 conflicts
0x52c63247…ce02
0x0a3323…0a3c
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