← previous blocknext block →recent activity

Analyzing

Block #73,753,351

10 transactions · 10 stateful · 2026-05-10 21:28:31 UTC

Parallelism

70/100

Blocked

20%

Avg conflicts / tx

0.3

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,753,351  ·  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

0x0eac6378…36f4

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x070a562a…8147

0x34b655…2a6f

6 touches
3 conflicts

0xbd2af710…34d9

0x1efe02…37d6

2 touches
0 conflicts

0x00000000…0002

0xab3526…fa38

2 touches
0 conflicts

0x3dbd9177…e936

0xea1b8e…c5ec

2 touches
0 conflicts

0x455b104f…3960

0xea1b8e…c5ec

2 touches
0 conflicts

0x6a35f85c…0190

0xea1b8e…c5ec

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

3 conflicts on slot 0x0eac637818…cb36f4

← previous block·next block →recent activity