← previous blocknext block →recent activity

Analyzing

Block #73,846,411

9 transactions · 8 stateful · 2026-05-11 07:52:27 UTC

Parallelism

56/100

Blocked

38%

Avg conflicts / tx

0.67

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,846,411  ·  9 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x4d87512b…897c

0x065c9d…c394

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x06161458…e6eb

0x065c9d…c394

4 touches
1 conflict

0xffc08657…58bb

0x065c9d…c394

3 touches
1 conflict

0x35e35d0a…0191

0x065c9d…c394

3 touches
1 conflict

0x4e7ddc7b…04ca

0x065c9d…c394

2 touches
0 conflicts

0x630dfaa4…b4ff

0x065c9d…c394

2 touches
0 conflicts

0xc2ca855c…dd2a

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

3 conflicts on slot 0x4d87512b00…43897c

← previous block·next block →recent activity