← previous blocknext block →recent activity

Analyzing

Block #73,201,058

6 transactions · 6 stateful · 2026-05-08 08:02:25 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,201,058  ·  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

0x602ff3d4…3ebd

0x34b655…2a6f

4 touches
1 conflict

0x6b6dbe88…d7f7

0x34b655…2a6f

4 touches
1 conflict

0x388e001a…7e04

0x34b655…2a6f

4 touches
1 conflict

0x8db1e0f2…2fcf

0x34b655…2a6f

4 touches
1 conflict

0x908d4442…2c4b

0x34b655…2a6f

2 touches
0 conflicts

0xac8e97a0…8426

0x34b655…2a6f

2 touches
0 conflicts

0xeb038f89…31d3

0x34b655…2a6f

2 touches
0 conflicts

0xf6476f21…3580

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 0x602ff3d41c…333ebd

← previous block·next block →recent activity