← previous blocknext block →recent activity

Analyzing

Block #73,338,870

11 transactions · 9 stateful · 2026-05-08 23:19:11 UTC

Parallelism

73/100

Blocked

22%

Avg conflicts / tx

0.18

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,338,870  ·  11 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

0x4546ebad…b908

0x34b655…2a6f

4 touches
1 conflict

0xac206e47…ef7d

0x34b655…2a6f

4 touches
1 conflict

0xb389d45f…8a4c

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x33f2d9b1…b689

0x34b655…2a6f

2 touches
0 conflicts

0x403295dc…8fb0

0x34b655…2a6f

2 touches
0 conflicts

0x66149d3e…b214

0x34b655…2a6f

2 touches
0 conflicts

0x693d979a…f2bd

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 0x4546ebad25…adb908

← previous block·next block →recent activity