← previous blocknext block →recent activity

Analyzing

Block #73,324,543

11 transactions · 11 stateful · 2026-05-08 21:43:57 UTC

Parallelism

82/100

Blocked

9%

Avg conflicts / tx

0.18

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,324,543  ·  11 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

0x2fe4467b…dd70

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x00f245ce…1e10

0x34b655…2a6f

2 touches
0 conflicts

0x0f9b918b…212d

0x34b655…2a6f

2 touches
0 conflicts

0x0ff2a7de…d418

0x34b655…2a6f

2 touches
0 conflicts

0x15c9b5bf…f732

0x34b655…2a6f

2 touches
0 conflicts

0x1b9e654e…0a08

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 0x2fe4467bcc…46dd70

← previous block·next block →recent activity