← previous blocknext block →recent activity

Analyzing

Block #73,970,403

14 transactions · 13 stateful · 2026-05-11 21:38:15 UTC

Parallelism

57/100

Blocked

46%

Avg conflicts / tx

1.21

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,970,403  ·  14 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0xf537eaa0…73c8

0x065c9d…c394

10 touches
10 conflicts

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x0eac6378…36f4

0x34b655…2a6f

2 touches
0 conflicts

0x129e2aad…879b

0x34b655…2a6f

2 touches
0 conflicts

0x1f336f28…2355

0x34b655…2a6f

2 touches
0 conflicts

0x33f2d9b1…b689

0x34b655…2a6f

2 touches
0 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: 0x065c9d28…a9c394

10 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity