← previous blocknext block →recent activity
Analyzing
Block #80,297,931
13 transactions · 11 stateful · 2026-06-10 05:14:57 UTC
Parallelism
77/100
Blocked
18%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,297,931 · 13 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
4w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d68b808…c6e3
0x34b655…2a6f
4 touches
1 conflict
0xc5ed5f80…43d0
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x5540f956…69e8
0x065c9d…c394
2 touches
0 conflicts
0x972f9474…067f
0x065c9d…c394
2 touches
0 conflicts
0xc122662f…3bf4
0x065c9d…c394
2 touches
0 conflicts
0xc790e3fb…a232
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 0x7d68b80863…c0c6e3
Audit this contract →
← previous block·next block →recent activity