← previous blocknext block →recent activity

Analyzing

Block #73,483,217

14 transactions · 12 stateful · 2026-05-09 15:19:38 UTC

Parallelism

57/100

Blocked

42%

Avg conflicts / tx

1.07

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,483,217  ·  14 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

0x046a928e…0012

0x2a68ba…90c5

12 touches
15 conflicts

0xf537eaa0…73c8

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x06db03a6…4692

0x34b655…2a6f

2 touches
0 conflicts

0x1b5d2e60…99b5

0x34b655…2a6f

2 touches
0 conflicts

0x2133b2da…fd22

0x34b655…2a6f

2 touches
0 conflicts

0x72c32214…4377

0x34b655…2a6f

2 touches
0 conflicts

0x85a88798…f85e

0x34b655…2a6f

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: 0x2a68ba18…8e90c5

15 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity