← previous blocknext block →recent activity

Analyzing

Block #73,492,544

8 transactions · 7 stateful · 2026-05-09 16:21:48 UTC

Parallelism

63/100

Blocked

29%

Avg conflicts / tx

0.25

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,492,544  ·  8 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

0x56a919c4…ab49

0xee8c0e…1242

4 touches
1 conflict

0x8876d94c…8435

0x2a68ba…90c5

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x4ae4a6c2…4755

0xa6afd3…d132

4 touches
1 conflict

0x11b69a7e…334e

0xee8c0e…1242

4 touches
1 conflict

0x00d4737d…1e87

0xd32edf…ff58

3 touches
1 conflict

0x729c91b8…9539

0x188d58…ea8e

2 touches
0 conflicts

0x00000000…0013

0x1b6862…e19c

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: 0xee8c0e9f…481242

1 conflict on slot 0x56a919c43e…27ab49

← previous block·next block →recent activity