← previous blocknext block →recent activity

Analyzing

Block #73,609,558

13 transactions · 12 stateful · 2026-05-10 05:19:33 UTC

Parallelism

77/100

Blocked

33%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,609,558  ·  13 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x5e6f50d0…28c5

0x34b655…2a6f

6 touches
3 conflicts

0x62857d27…ccf0

0x34b655…2a6f

6 touches
3 conflicts

0x9ea57326…329f

0x34b655…2a6f

6 touches
3 conflicts

0xae69c125…2379

0x2a68ba…90c5

4 touches
1 conflict

0xc9e97522…3519

0x2a68ba…90c5

4 touches
1 conflict

0x0175b7a6…1dba

0x6c4bfa…a540

4 touches
1 conflict

0x0175b7a6…1dbb

0x6c4bfa…a540

4 touches
1 conflict

0x1a4b4152…0a08

0x6c4bfa…a540

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: 0x34b6552d…112a6f

3 conflicts on slot 0x5e6f50d077…2928c5

← previous block·next block →recent activity