← previous blocknext block →recent activity

Analyzing

Block #73,396,880

9 transactions · 9 stateful · 2026-05-09 05:45:08 UTC

Parallelism

67/100

Blocked

22%

Avg conflicts / tx

0.44

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,396,880  ·  9 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

0x273d80cd…9ecc

0x34b655…2a6f

6 touches
3 conflicts

0xcc6521c1…c892

0x8d66a4…3095

4 touches
1 conflict

0xa91c899f…6ee3

0x34b655…2a6f

4 touches
1 conflict

0xedb848fe…6534

0x34b655…2a6f

4 touches
1 conflict

0x462c8be7…4f83

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1ab

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1ad

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1ae

0x8d66a4…3095

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 0x273d80cd54…519ecc

← previous block·next block →recent activity