← previous blocknext block →recent activity

Analyzing

Block #73,324,191

26 transactions · 16 stateful · 2026-05-08 21:41:36 UTC

Parallelism

73/100

Blocked

50%

Avg conflicts / tx

0.65

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,324,191  ·  26 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xd18f575a…d2d8

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x8d0dfe2c…3345

0x2a68ba…90c5

4 touches
1 conflict

0xf537eaa0…73c8

0x065c9d…c394

4 touches
1 conflict

0x5d82c9b5…004c

0x3bd359…433a

2 touches
0 conflicts

0x09000000…0001

0x000000…1000

2 touches
0 conflicts

0x00000000…0004

0x5afd3e…7620

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

10 conflicts on slot 0xd18f575a22…e0d2d8

← previous block·next block →recent activity