← previous blocknext block →recent activity

Analyzing

Block #73,492,536

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

Parallelism

57/100

Blocked

43%

Avg conflicts / tx

0.86

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

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

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x22e295f5…1bef

0x065c9d…c394

4 touches
1 conflict

0x956ff66e…ace9

0x065c9d…c394

2 touches
0 conflicts

0xa3bca023…6194

0x065c9d…c394

2 touches
0 conflicts

0xed03d073…291d

0x065c9d…c394

2 touches
0 conflicts

0xf44cc08a…a344

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

3 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity