← previous blocknext block →recent activity

Analyzing

Block #73,261,104

16 transactions · 9 stateful · 2026-05-08 14:41:42 UTC

Parallelism

88/100

Blocked

11%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,261,104  ·  16 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

0x7791196a…695b

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0x6cab9ef4…f849

0x34b655…2a6f

4 touches
1 conflict

0x76ed8777…1e5f

0x34b655…2a6f

4 touches
1 conflict

0x5e1c23e9…4f81

0x34b655…2a6f

2 touches
0 conflicts

0x696cb728…4526

0x34b655…2a6f

2 touches
0 conflicts

0x791b1ae7…0a63

0x34b655…2a6f

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

1 conflict on slot 0x7791196a24…b9695b

← previous block·next block →recent activity