← previous blocknext block →recent activity

Analyzing

Block #73,923,937

18 transactions · 17 stateful · 2026-05-11 16:29:09 UTC

Parallelism

78/100

Blocked

24%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,923,937  ·  18 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

0xf537eaa0…73c8

0x065c9d…c394

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xdd4096d6…3f51

0x7b2728…7777

2 touches
1 conflict

0x00000000…0000

0x3e1523…94aa

2 touches
0 conflicts

0x00000000…0002

0x3e1523…94aa

2 touches
0 conflicts

0x00000000…0003

0x3e1523…94aa

2 touches
0 conflicts

0x00000000…000e

0x3e1523…94aa

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: 0x065c9d28…a9c394

6 conflicts on slot 0xf537eaa0c6…3873c8

← previous block·next block →recent activity