← previous blocknext block →recent activity

Analyzing

Block #73,981,908

12 transactions · 10 stateful · 2026-05-11 22:55:33 UTC

Parallelism

67/100

Blocked

30%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,981,908  ·  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

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0x6f08361d…bda6

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x2aab0897…78f7

0x34b655…2a6f

2 touches
0 conflicts

0xfe39a1f7…8eb0

0x34b655…2a6f

2 touches
0 conflicts

0x0d622e34…0000

0x681e90…ae09

2 touches
0 conflicts

0x7f430e47…4cbd

0x8d66a4…3095

2 touches
0 conflicts

0x8a35acfb…d1aa

0x8d66a4…3095

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 0xf2f76ab392…f3623e

← previous block·next block →recent activity