← previous blocknext block →recent activity

Analyzing

Block #73,493,272

29 transactions · 20 stateful · 2026-05-09 16:26:37 UTC

Parallelism

83/100

Blocked

50%

Avg conflicts / tx

0.69

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,493,272  ·  29 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0x1c354dc0…96de

0x754704…b603

8 touches
6 conflicts

0x6af306bb…2e81

0x3bd359…433a

8 touches
6 conflicts

0xf91b744e…9117

0x754704…b603

8 touches
6 conflicts

0xf4135f0b…159e

0xd32edf…ff58

7 touches
6 conflicts

0xdd70bea3…1ffe

0x3bd359…433a

6 touches
3 conflicts

0x00000000…0028

0x1b6862…e19c

4 touches
1 conflict

0x6aa624fd…a84b

0x1b6862…e19c

4 touches
1 conflict

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: 0x754704bc…afb603

6 conflicts on slot 0x17606ba612…ea1b6e

← previous block·next block →recent activity