← previous blocknext block →recent activity
Analyzing
Block #80,650,630
18 transactions · 15 stateful · 2026-06-11 20:27:00 UTC
Parallelism
56/100
Blocked
47%
Avg conflicts / tx
1.56
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #80,650,630 · 18 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
10w011w112w213w314w415w516w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x326a02b5…8dad
0x34b655…2a6f
8 touches
6 conflicts
0x6fbc2e5a…e69c
0x34b655…2a6f
8 touches
6 conflicts
0x0ad4dbe8…ae93
0x34b655…2a6f
6 touches
3 conflicts
0x496ff651…1310
0x34b655…2a6f
5 touches
3 conflicts
0x8e6a04af…c5e5
0x34b655…2a6f
4 touches
1 conflict
0xbb12db23…857e
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
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity