← previous blocknext block →recent activity

Analyzing

Block #73,744,716

27 transactions · 20 stateful · 2026-05-10 20:30:14 UTC

Parallelism

67/100

Blocked

60%

Avg conflicts / tx

1.26

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #73,744,716  ·  27 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

12 touches
15 conflicts

0xdbf974a4…b232

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x5de96bd3…c60c

0x34b655…2a6f

8 touches
6 conflicts

0xaa8a1c54…ead3

0x34b655…2a6f

6 touches
3 conflicts

0x8a35acfb…d1ae

0x8d66a4…3095

6 touches
3 conflicts

0xe13f4efe…3ac7

0x34b655…2a6f

6 touches
3 conflicts

0xba91de06…67cc

0x34b655…2a6f

6 touches
3 conflicts

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity