← previous blocknext block →recent activity

Analyzing

Block #73,683,486

12 transactions · 11 stateful · 2026-05-10 13:37:12 UTC

Parallelism

67/100

Blocked

45%

Avg conflicts / tx

0.67

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,683,486  ·  12 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

6 touches
3 conflicts

0x0ac31945…2c72

0x065c9d…c394

6 touches
3 conflicts

0x1a95c7e8…5894

0x065c9d…c394

4 touches
1 conflict

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0x8e9cb7cc…da4b

0x065c9d…c394

4 touches
1 conflict

0x613f2733…b223

0x065c9d…c394

3 touches
1 conflict

0x37af7524…07ea

0x065c9d…c394

3 touches
1 conflict

0xbcd6598b…2aa0

0x065c9d…c394

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

3 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity