← previous blocknext block →recent activity

Analyzing

Block #73,601,706

9 transactions · 9 stateful · 2026-05-10 04:27:19 UTC

Parallelism

78/100

Blocked

11%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,601,706  ·  9 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x09e17a93…675f

0x065c9d…c394

2 touches
0 conflicts

0x00000000…000d

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0016

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…001a

0x1b6862…e19c

2 touches
0 conflicts

0xebd4104a…098e

0x1b6862…e19c

2 touches
0 conflicts

0x01a89030…f786

0x368ee5…7ca4

2 touches
0 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: 0x2a68ba18…8e90c5

1 conflict on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity