← previous blocknext block →recent activity
Analyzing
Block #80,476,514
13 transactions · 10 stateful · 2026-06-11 01:05:08 UTC
Parallelism
85/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,476,514 · 13 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
11w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x537e2e5b…c3ab
0x34b655…2a6f
4 touches
1 conflict
0xd92a03c7…bfc7
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x743b84ed…2845
0x000000…8ba3
2 touches
0 conflicts
0x9fd9b22a…cb4a
0x000000…8ba3
2 touches
0 conflicts
0x0b719ae1…3fb9
0x188d58…ea8e
2 touches
0 conflicts
0x0b719ae1…3fba
0x188d58…ea8e
2 touches
0 conflicts
0x0b719ae1…3fbb
0x188d58…ea8e
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 0x537e2e5b8c…c7c3ab
Audit this contract →
← previous block·next block →recent activity