← previous blocknext block →recent activity

Analyzing

Block #73,647,097

9 transactions · 8 stateful · 2026-05-10 09:31:38 UTC

Parallelism

67/100

Blocked

25%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,647,097  ·  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

0x8a2657f5…e008

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x24400a9f…ff5d

0x34b655…2a6f

2 touches
0 conflicts

0x2eab2661…2b15

0x34b655…2a6f

2 touches
0 conflicts

0xab1e6e73…34fd

0x34b655…2a6f

2 touches
0 conflicts

0xac206e47…ef7d

0x34b655…2a6f

2 touches
0 conflicts

0xb82bffbd…c6de

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

3 conflicts on slot 0x8a2657f5c3…4ce008

← previous block·next block →recent activity