← previous blocknext block →recent activity

Analyzing

Block #73,476,219

10 transactions · 9 stateful · 2026-05-09 14:33:07 UTC

Parallelism

70/100

Blocked

22%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,476,219  ·  10 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

0x718e8448…963b

0xd32edf…ff58

5 touches
3 conflicts

0x6f08361d…bda6

0x065c9d…c394

4 touches
1 conflict

0xf537eaa0…73c8

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x08d73a61…529e

0x065c9d…c394

2 touches
0 conflicts

0x6745bc83…04c4

0x065c9d…c394

2 touches
0 conflicts

0xae69c125…2379

0x2a68ba…90c5

2 touches
0 conflicts

0x09000000…0001

0x000000…1000

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: 0xd32edf66…9fff58

3 conflicts on slot 0x718e844876…ad963b

← previous block·next block →recent activity