← previous blocknext block →recent activity

Analyzing

Block #73,809,515

12 transactions · 9 stateful · 2026-05-11 03:47:00 UTC

Parallelism

75/100

Blocked

33%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,809,515  ·  12 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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xe35b171a…b47b

0x065c9d…c394

4 touches
1 conflict

0x22e295f5…1bef

0x065c9d…c394

4 touches
1 conflict

0x21a14a06…3901

0x065c9d…c394

3 touches
1 conflict

0xdf91d78e…1333

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0009

0x0c65a0…0852

2 touches
0 conflicts

0x3959cfa5…1dc8

0x0c65a0…0852

2 touches
0 conflicts

0xa5e083bb…11e7

0x0c65a0…0852

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 0x0000000000…00003d

← previous block·next block →recent activity