Block #73,201,224

← previous blocknext block →recent activity

Analyzing

Block #73,201,224

16 transactions · 15 stateful · 2026-05-08 08:03:31 UTC

Parallelism

63/100

Blocked

40%

Avg conflicts / tx

1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,201,224  ·  16 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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…0002

0xab3526…fa38

12 touches
15 conflicts

0x7f189cf6…afab

0x065c9d…c394

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x6b3d34c5…8169

0x065c9d…c394

2 touches
0 conflicts

0x6dd2ce3b…4b16

0x065c9d…c394

2 touches
0 conflicts

0x8e66da19…66b6

0x065c9d…c394

2 touches
0 conflicts

0xc787c8f0…5e13

0x065c9d…c394

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: 0xab35264b…1cfa38

15 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity