← previous blocknext block →recent activity
Analyzing
Block #80,299,946
18 transactions · 13 stateful · 2026-06-10 05:28:23 UTC
Parallelism
61/100
Blocked
54%
Avg conflicts / tx
1.22
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #80,299,946 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w09w110w211w313w414w515w116w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x2d5ef110…3446
0x34b655…2a6f
6 touches
3 conflicts
0x58397d66…a6bc
0x34b655…2a6f
6 touches
3 conflicts
0x1d351a9b…f2dd
0x34b655…2a6f
6 touches
3 conflicts
0x82ded54c…06f6
0x34b655…2a6f
5 touches
3 conflicts
0x678a8de3…7da5
0x34b655…2a6f
4 touches
1 conflict
0x7c6d3d6d…9deb
0x34b655…2a6f
4 touches
1 conflict
0x6f6b4878…d72d
0x34b655…2a6f
4 touches
1 conflict
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
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity