← previous blocknext block →recent activity

Analyzing

Block #73,652,192

7 transactions · 7 stateful · 2026-05-10 10:05:54 UTC

Parallelism

71/100

Blocked

14%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,652,192  ·  7 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

0x2ad0f4b3…6b5b

0x34b655…2a6f

4 touches
1 conflict

0x38524fae…9deb

0x34b655…2a6f

4 touches
1 conflict

0xb0ddfb02…e9e6

0x34b655…2a6f

4 touches
1 conflict

0xbc20a344…ce63

0x34b655…2a6f

4 touches
1 conflict

0x34e136b1…0442

0x065c9d…c394

2 touches
0 conflicts

0x3efdef11…c7db

0x065c9d…c394

2 touches
0 conflicts

0x7251226b…613d

0x065c9d…c394

2 touches
0 conflicts

0xb159af88…a9e7

0x065c9d…c394

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

1 conflict on slot 0x2ad0f4b3dd…116b5b

← previous block·next block →recent activity