← previous blocknext block →recent activity

Analyzing

Block #73,979,074

27 transactions · 26 stateful · 2026-05-11 22:36:31 UTC

Parallelism

56/100

Blocked

62%

Avg conflicts / tx

2.89

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #73,979,074  ·  27 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

0xb4b3c404…f0aa

0x3bd359…433a

24 touches
66 conflicts

0x00000000…0000

0x579d00…83f8

24 touches
66 conflicts

0x00000000…0002

0x579d00…83f8

24 touches
66 conflicts

0x00000000…0003

0x579d00…83f8

24 touches
66 conflicts

0x399cd013…b14f

0x23ae8c…7777

24 touches
66 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x6f08361d…bda6

0x065c9d…c394

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

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: 0x3bd359c1…15433a

66 conflicts on slot 0xb4b3c404bb…77f0aa

← previous block·next block →recent activity