← previous blocknext block →recent activity

Analyzing

Block #73,647,106

13 transactions · 11 stateful · 2026-05-10 09:31:41 UTC

Parallelism

77/100

Blocked

27%

Avg conflicts / tx

0.31

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

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

0x22e295f5…1bef

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x7cb2f3fa…4836

0x34b655…2a6f

2 touches
0 conflicts

0xac808a27…82db

0x34b655…2a6f

2 touches
0 conflicts

0x06956408…967b

0x754704…b603

2 touches
0 conflicts

0x2539f796…e968

0x754704…b603

2 touches
0 conflicts

0xfd4bd0e6…5918

0x754704…b603

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: 0x065c9d28…a9c394

3 conflicts on slot 0x22e295f5d8…ac1bef

← previous block·next block →recent activity