← previous blocknext block →recent activity

Analyzing

Block #73,337,828

21 transactions · 17 stateful · 2026-05-08 23:12:15 UTC

Parallelism

57/100

Blocked

53%

Avg conflicts / tx

1.57

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #73,337,828  ·  21 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

0x724fc7fc…ebd2

0xd32edf…ff58

15 touches
28 conflicts

0xa1087a5c…66c4

0x754704…b603

8 touches
6 conflicts

0x8d0dfe2c…3345

0x2a68ba…90c5

8 touches
6 conflicts

0xc8e4d41c…13c4

0x065c9d…c394

8 touches
6 conflicts

0x00000000…001d

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002d

0x1b6862…e19c

4 touches
1 conflict

0xb1526c23…f2b9

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

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

28 conflicts on slot 0x724fc7fc85…aeebd2

← previous block·next block →recent activity