← previous blocknext block →recent activity

Analyzing

Block #73,343,432

31 transactions · 26 stateful · 2026-05-08 23:49:32 UTC

Parallelism

55/100

Blocked

65%

Avg conflicts / tx

2.26

Longest chain

14 deep

Execution timeline

did this block parallelize well?

view

block #73,343,432  ·  31 txs across 14 waves  ·  depth 14
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

wave w12

wave w13

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

0x799b3d3e…a4b7

0xd32edf…ff58

19 touches
45 conflicts

0x6f08361d…bda6

0x065c9d…c394

12 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

12 touches
15 conflicts

0x00000000…0013

0x1b6862…e19c

10 touches
10 conflicts

0xf537eaa0…73c8

0x065c9d…c394

10 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

10 touches
10 conflicts

0x44d7acbf…e67f

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 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

45 conflicts on slot 0x799b3d3e9f…7aa4b7

← previous block·next block →recent activity