← previous blocknext block →recent activity

Analyzing

Block #73,473,843

18 transactions · 12 stateful · 2026-05-09 14:17:18 UTC

Parallelism

83/100

Blocked

33%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,473,843  ·  18 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

0xa91c899f…6ee3

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0x868859b9…3db5

0x34b655…2a6f

4 touches
1 conflict

0x908d4442…2c4b

0x34b655…2a6f

4 touches
1 conflict

0xc6417de0…2191

0xc8689a…ee79

4 touches
1 conflict

0x99f080dc…58c1

0x34b655…2a6f

4 touches
1 conflict

0xedb848fe…6534

0x34b655…2a6f

4 touches
1 conflict

0x57de3828…3fbb

0x34b655…2a6f

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: 0x34b6552d…112a6f

3 conflicts on slot 0xa91c899f02…fa6ee3

← previous block·next block →recent activity