← previous blocknext block →recent activity

Analyzing

Block #73,490,592

34 transactions · 17 stateful · 2026-05-09 16:08:49 UTC

Parallelism

79/100

Blocked

65%

Avg conflicts / tx

0.88

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,490,592  ·  34 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

0xf5494d09…1635

0xd32edf…ff58

13 touches
21 conflicts

0x2877f440…c2c8

0x34b655…2a6f

6 touches
3 conflicts

0xd06cc746…27e4

0x350035…7777

6 touches
3 conflicts

0x00000000…0003

0x116e7d…d8f1

4 touches
1 conflict

0x0f44ce3c…7e23

0x350035…7777

4 touches
1 conflict

0x692a4122…76b8

0x350035…7777

4 touches
1 conflict

0xf4381dd7…e66b

0x350035…7777

4 touches
1 conflict

0x0983b8c8…4d94

0x3bd359…433a

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

21 conflicts on slot 0xf5494d09d0…331635

← previous block·next block →recent activity