← previous blocknext block →recent activity

Analyzing

Block #73,695,904

12 transactions · 10 stateful · 2026-05-10 15:00:48 UTC

Parallelism

67/100

Blocked

40%

Avg conflicts / tx

0.58

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,695,904  ·  12 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xf2438038…5fa7

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0x9a43401f…9d06

0x34b655…2a6f

4 touches
1 conflict

0x218e3595…b7ca

0x34b655…2a6f

4 touches
1 conflict

0xcdf15f50…8ae7

0x34b655…2a6f

4 touches
1 conflict

0xd9376757…e708

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0002

0xab3526…fa38

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

6 conflicts on slot 0xf2438038b6…475fa7

← previous block·next block →recent activity