← previous blocknext block →recent activity

Analyzing

Block #73,578,513

16 transactions · 13 stateful · 2026-05-10 01:53:03 UTC

Parallelism

88/100

Blocked

15%

Avg conflicts / tx

0.19

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,578,513  ·  16 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

0xc2e8bece…67d9

0x34b655…2a6f

4 touches
1 conflict

0x462c8be7…4f83

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1ab

0x8d66a4…3095

4 touches
1 conflict

0xd0f6f4f2…dffa

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0x2013846c…a7a7

0x34b655…2a6f

2 touches
0 conflicts

0xea02471d…1539

0x34b655…2a6f

2 touches
0 conflicts

0x0d622e34…0000

0x681e90…ae09

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 0xc2e8beced0…cb67d9

← previous block·next block →recent activity