← previous blocknext block →recent activity

Analyzing

Block #80,250,999

25 transactions · 23 stateful · 2026-06-10 00:02:10 UTC

Parallelism

60/100

Blocked

57%

Avg conflicts / tx

2

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #80,250,999  ·  25 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x9f4e12e3…21c7

0x336ed4…c59c

20 touches
45 conflicts

0x00000000…000a

0x90c374…be45

20 touches
45 conflicts

0x00000000…000b

0x90c374…be45

20 touches
45 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x00000000…002f

0x1b6862…e19c

4 touches
1 conflict

0x93afca4c…b47f

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

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: 0x336ed437…cfc59c

45 conflicts on slot 0x9f4e12e393…0a21c7

← previous block·next block →recent activity