← previous blocknext block →recent activity

Analyzing

Block #73,654,051

12 transactions · 11 stateful · 2026-05-10 10:18:27 UTC

Parallelism

67/100

Blocked

45%

Avg conflicts / tx

0.75

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,654,051  ·  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

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x51087f5a…61f7

0x34b655…2a6f

4 touches
1 conflict

0x69941f7e…3b1d

0x34b655…2a6f

4 touches
1 conflict

0x757254ae…d917

0x34b655…2a6f

3 touches
1 conflict

0x84630c7f…21f4

0x065c9d…c394

3 touches
1 conflict

0xdbadf6b0…43b2

0x33176b…e078

2 touches
0 conflicts

0x01a89030…f786

0x98dc6e…8633

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: 0x2a68ba18…8e90c5

6 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity