← previous blocknext block →recent activity
Analyzing
Block #80,266,161
17 transactions · 15 stateful · 2026-06-10 01:43:17 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,266,161 · 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
4w05w06w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1d351a9b…f2dd
0x34b655…2a6f
4 touches
1 conflict
0xc38151f2…2bcb
0xc8689a…ee79
4 touches
1 conflict
0x9495bffc…46e6
0x34b655…2a6f
4 touches
1 conflict
0x8b305a3b…1c34
0x34b655…2a6f
4 touches
1 conflict
0xd5ef0dbd…0afd
0x34b655…2a6f
3 touches
1 conflict
0x9fc8b97d…96da
0x2a68ba…90c5
2 touches
0 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
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 0x1d351a9b20…2df2dd
Audit this contract →
← previous block·next block →recent activity