← previous blocknext block →recent activity

Analyzing

Block #73,809,481

14 transactions · 11 stateful · 2026-05-11 03:46:46 UTC

Parallelism

64/100

Blocked

36%

Avg conflicts / tx

0.71

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,809,481  ·  14 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x046a928e…0012

0x2a68ba…90c5

10 touches
10 conflicts

0x22e295f5…1bef

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0003

0x059114…ac3b

4 touches
1 conflict

0xcf83d84d…ff3e

0x3bd359…433a

4 touches
1 conflict

0x55c005b1…848f

0x059114…ac3b

4 touches
1 conflict

0x773d4fb9…d34d

0x754704…b603

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x81b44058…bcce

0x059114…ac3b

4 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

10 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity