← previous blocknext block →recent activity

Analyzing

Block #73,598,242

8 transactions · 5 stateful · 2026-05-10 04:04:14 UTC

Parallelism

75/100

Blocked

20%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,598,242  ·  8 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xa5a584d1…c457

0x065c9d…c394

3 touches
1 conflict

0x4ae4a77a…76e6

0x065c9d…c394

3 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x22e295f5…1bef

0x065c9d…c394

2 touches
0 conflicts

0x32a9d34f…a94d

0x065c9d…c394

2 touches
0 conflicts

0x4d87512b…897c

0x065c9d…c394

2 touches
0 conflicts

0x97daf98a…da3b

0x065c9d…c394

2 touches
0 conflicts

0x60b24061…7c23

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

1 conflict on slot 0xa5a584d113…bac457

← previous block·next block →recent activity