← previous blocknext block →recent activity

Analyzing

Block #73,694,824

23 transactions · 17 stateful · 2026-05-10 14:53:33 UTC

Parallelism

65/100

Blocked

53%

Avg conflicts / tx

1.09

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,694,824  ·  23 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x54a0ef59…b6c8

0xd32edf…ff58

11 touches
15 conflicts

0x529acb6a…fcc6

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x0ac31945…2c72

0x065c9d…c394

6 touches
3 conflicts

0x00000000…001c

0x1b6862…e19c

4 touches
1 conflict

0xc3c8642a…7da5

0x2a68ba…90c5

4 touches
1 conflict

0x14845934…d13c

0x34b655…2a6f

4 touches
1 conflict

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 0x54a0ef5978…5eb6c8

← previous block·next block →recent activity