← previous blocknext block →recent activity

Analyzing

Block #73,035,174

31 transactions · 23 stateful · 2026-05-07 13:38:38 UTC

Parallelism

71/100

Blocked

70%

Avg conflicts / tx

1.29

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #73,035,174  ·  31 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xe09eda07…8dda

0x2a68ba…90c5

12 touches
15 conflicts

0xa1087a5c…66c4

0x754704…b603

10 touches
10 conflicts

0xea7b5736…47f4

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…0002

0xd574ca…7ab1

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0xba5743c7…21c6

0x1b6862…e19c

8 touches
6 conflicts

0xe53866e6…1888

0x065c9d…c394

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

15 conflicts on slot 0xe09eda075e…748dda

← previous block·next block →recent activity