← previous blocknext block →recent activity

Analyzing

Block #73,490,503

25 transactions · 16 stateful · 2026-05-09 16:08:14 UTC

Parallelism

72/100

Blocked

44%

Avg conflicts / tx

1

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,490,503  ·  25 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x062b26b8…d9c7

0xd32edf…ff58

13 touches
21 conflicts

0x3923d7de…bb41

0x754704…b603

6 touches
3 conflicts

0x81955a0a…29ee

0x6657d1…8ccc

6 touches
3 conflicts

0xeeb8b7fc…24d6

0x6657d1…8ccc

6 touches
3 conflicts

0x532ec3cc…707a

0x6657d1…8ccc

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0xcb45d9d6…cb80

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0018

0x1b6862…e19c

6 touches
3 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: 0xd32edf66…9fff58

21 conflicts on slot 0x062b26b852…60d9c7

← previous block·next block →recent activity