← previous blocknext block →recent activity

Analyzing

Block #73,478,216

8 transactions · 7 stateful · 2026-05-09 14:46:23 UTC

Parallelism

63/100

Blocked

29%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,478,216  ·  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

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x6f08361d…bda6

0x065c9d…c394

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x5e11e756…bde2

0x065c9d…c394

2 touches
0 conflicts

0xa5b153ae…5e64

0x065c9d…c394

2 touches
0 conflicts

0x0dbf9688…c6cf

0x10aeaf…5417

2 touches
0 conflicts

0x36cd3056…b5d4

0x188d58…ea8e

2 touches
0 conflicts

0x36cd3056…b5d5

0x188d58…ea8e

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: 0x2a68ba18…8e90c5

3 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity