← previous blocknext block →recent activity
Analyzing
Block #80,240,896
17 transactions · 10 stateful · 2026-06-09 22:54:49 UTC
Parallelism
88/100
Blocked
10%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,240,896 · 17 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
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x96d14afa…41ed
0x34b655…2a6f
4 touches
1 conflict
0x90f07a4f…d932
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x181dd265…e12c
0x34b655…2a6f
2 touches
0 conflicts
0x2e93ce0b…38fd
0x34b655…2a6f
2 touches
0 conflicts
0x37421b44…45b5
0x34b655…2a6f
2 touches
0 conflicts
0x4b5f8927…7742
0x34b655…2a6f
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 0x96d14afa46…c341ed
Audit this contract →
← previous block·next block →recent activity