← previous blocknext block →recent activity

Analyzing

Block #73,924,274

26 transactions · 21 stateful · 2026-05-11 16:31:23 UTC

Parallelism

77/100

Blocked

57%

Avg conflicts / tx

1.23

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,924,274  ·  26 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

0x4a0ec475…ed71

0xd32edf…ff58

11 touches
15 conflicts

0xf537eaa0…73c8

0x065c9d…c394

10 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x93afca4c…b479

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0019

0x1b6862…e19c

6 touches
3 conflicts

0x6f08361d…bda6

0x065c9d…c394

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

15 conflicts on slot 0x4a0ec47508…ebed71

← previous block·next block →recent activity