← previous blocknext block →recent activity

Analyzing

Block #73,706,344

25 transactions · 18 stateful · 2026-05-10 16:11:15 UTC

Parallelism

68/100

Blocked

50%

Avg conflicts / tx

1.16

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,706,344  ·  25 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0x9dc9fa5f…7f23

0x34b655…2a6f

6 touches
3 conflicts

0x78e3ec57…8bf9

0x34b655…2a6f

6 touches
3 conflicts

0x1218ce79…2c23

0xd32edf…ff58

5 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x849f3e33…c095

0x34b655…2a6f

4 touches
1 conflict

0x8a85cf3d…2868

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

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity