← previous blocknext block →recent activity
Analyzing
Block #80,760,700
51 transactions · 16 stateful · 2026-06-12 08:40:54 UTC
Parallelism
88/100
Blocked
44%
Avg conflicts / tx
0.25
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #80,760,700 · 51 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w010w020w123w235w344w148w349w450w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xf6476f21…3580
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xf6884b1c…8b7f
0x34b655…2a6f
4 touches
1 conflict
0xfa1a8731…ca65
0x34b655…2a6f
4 touches
1 conflict
0xfbabb02d…af07
0x34b655…2a6f
4 touches
1 conflict
0xfcfb570f…cf1c
0x34b655…2a6f
4 touches
1 conflict
0x213a54fa…c85f
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity