← previous blocknext block →recent activity

Analyzing

Block #73,343,729

32 transactions · 26 stateful · 2026-05-08 23:51:30 UTC

Parallelism

63/100

Blocked

73%

Avg conflicts / tx

2.94

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #73,343,729  ·  32 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

0xc84b20ec…f1ec

0xd32edf…ff58

23 touches
66 conflicts

0xbdff944d…447e

0x2a68ba…90c5

14 touches
21 conflicts

0xa1087a5c…66c4

0x754704…b603

12 touches
15 conflicts

0xacedfed1…aef2

0x065c9d…c394

9 touches
10 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001d

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…002d

0x1b6862…e19c

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: 0xd32edf66…9fff58

66 conflicts on slot 0xc84b20ec1a…fff1ec

← previous block·next block →recent activity