← previous blocknext block →recent activity

Analyzing

Block #73,683,193

10 transactions · 9 stateful · 2026-05-10 13:35:13 UTC

Parallelism

70/100

Blocked

44%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,683,193  ·  10 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

0x529acb6a…fcc6

0x065c9d…c394

6 touches
3 conflicts

0x3b646fdf…a83d

0x036056…1881

4 touches
1 conflict

0x50e95f24…254e

0x036056…1881

4 touches
1 conflict

0x5e1c7b89…cf47

0x036056…1881

4 touches
1 conflict

0x00000000…0007

0x09f880…ede0

4 touches
1 conflict

0x00000000…000a

0x09f880…ede0

4 touches
1 conflict

0xae69c125…2379

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…0003

0xab3526…fa38

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: 0x065c9d28…a9c394

3 conflicts on slot 0x529acb6ad1…f0fcc6

← previous block·next block →recent activity