← previous blocknext block →recent activity

Analyzing

Block #73,968,503

6 transactions · 5 stateful · 2026-05-11 21:25:34 UTC

Parallelism

67/100

Blocked

20%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,968,503  ·  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

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0xcb45d9d6…cb82

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001a

0x1b6862…e19c

4 touches
1 conflict

0xef65a5e3…23c5

0xd32edf…ff58

3 touches
1 conflict

0x71de8dd3…9ca7

0x065c9d…c394

2 touches
0 conflicts

0x8996f56c…3f9c

0x065c9d…c394

2 touches
0 conflicts

0xf537eaa0…73c8

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: 0x1b68626d…2de19c

1 conflict on slot 0x0000000000…000012

← previous block·next block →recent activity