← previous blocknext block →recent activity

Analyzing

Block #73,600,680

28 transactions · 24 stateful · 2026-05-10 04:20:30 UTC

Parallelism

61/100

Blocked

63%

Avg conflicts / tx

1.25

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #73,600,680  ·  28 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0x9db64d13…fb98

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x8a35acfb…d1aa

0x8d66a4…3095

6 touches
3 conflicts

0x00000000…001a

0x1b6862…e19c

4 touches
1 conflict

0xae69c125…2379

0x2a68ba…90c5

4 touches
1 conflict

0xc9e97522…3519

0x2a68ba…90c5

4 touches
1 conflict

0xcce2fd99…a8eb

0x3bd359…433a

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: 0x34b6552d…112a6f

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity