← previous blocknext block →recent activity

Analyzing

Block #73,807,281

6 transactions · 6 stateful · 2026-05-11 03:32:05 UTC

Parallelism

67/100

Blocked

17%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,807,281  ·  6 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

0xe824ec98…9e6f

0xd32edf…ff58

3 touches
1 conflict

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x335a161d…fe7f

0x000000…012a

2 touches
0 conflicts

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x56b7cf99…5924

0x065c9d…c394

2 touches
0 conflicts

0xb4626049…8c9a

0x065c9d…c394

2 touches
0 conflicts

0xc74552af…5981

0x065c9d…c394

2 touches
0 conflicts

0xd831db5a…971d

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: 0xd32edf66…9fff58

1 conflict on slot 0xe824ec980c…939e6f

← previous block·next block →recent activity