← previous blocknext block →recent activity

Analyzing

Block #73,807,060

14 transactions · 12 stateful · 2026-05-11 03:30:37 UTC

Parallelism

79/100

Blocked

25%

Avg conflicts / tx

0.36

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,807,060  ·  14 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0x973f9be7…4f61

0x34b655…2a6f

4 touches
1 conflict

0xd2facdba…7a7e

0x34b655…2a6f

4 touches
1 conflict

0xcf4f9e42…5e50

0x34b655…2a6f

2 touches
0 conflicts

0xbec3bb74…7bb9

0x754704…b603

2 touches
0 conflicts

0xeaa77724…550c

0x754704…b603

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity