← previous blocknext block →recent activity

Analyzing

Block #73,170,688

12 transactions · 11 stateful · 2026-05-08 04:39:59 UTC

Parallelism

75/100

Blocked

27%

Avg conflicts / tx

0.25

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,170,688  ·  12 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

0xe89e1a22…ce49

0x8d66a4…3095

4 touches
1 conflict

0x2877f440…c2c8

0x34b655…2a6f

4 touches
1 conflict

0xba9f88e8…9c33

0x34b655…2a6f

4 touches
1 conflict

0xbc7a7347…fc9a

0x34b655…2a6f

4 touches
1 conflict

0xd984a5e4…5cfc

0x34b655…2a6f

4 touches
1 conflict

0xf6476f21…3580

0x34b655…2a6f

4 touches
1 conflict

0x8a35acfb…d1aa

0x8d66a4…3095

4 touches
1 conflict

0xe09eda07…8dda

0x2a68ba…90c5

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: 0x8d66a43f…113095

1 conflict on slot 0xe89e1a2242…33ce49

← previous block·next block →recent activity