← previous blocknext block →recent activity

Analyzing

Block #73,961,037

18 transactions · 9 stateful · 2026-05-11 20:35:51 UTC

Parallelism

89/100

Blocked

22%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,961,037  ·  18 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

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0xfa0deecd…14fe

0xd32edf…ff58

3 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x0aec204a…4ba6

0x065c9d…c394

2 touches
0 conflicts

0x91be2281…55c4

0x065c9d…c394

2 touches
0 conflicts

0xb8852d56…bbb7

0x065c9d…c394

2 touches
0 conflicts

0xca95577c…fcd4

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 0xea02471df2…601542

← previous block·next block →recent activity