← previous blocknext block →recent activity

Analyzing

Block #73,476,164

6 transactions · 6 stateful · 2026-05-09 14:32:45 UTC

Parallelism

67/100

Blocked

17%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,476,164  ·  6 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

0xb389d45f…8a4c

0x34b655…2a6f

4 touches
1 conflict

0x2133b2da…fd22

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

2 touches
0 conflicts

0x0a80ff36…d8d4

0x34b655…2a6f

2 touches
0 conflicts

0x2a545780…c415

0x34b655…2a6f

2 touches
0 conflicts

0x388f889f…a655

0x34b655…2a6f

2 touches
0 conflicts

0x3df2cf9c…ce34

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 0xb389d45f2b…a98a4c

← previous block·next block →recent activity