← previous blocknext block →recent activity

Analyzing

Block #73,161,411

9 transactions · 8 stateful · 2026-05-08 03:38:20 UTC

Parallelism

67/100

Blocked

25%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,161,411  ·  9 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

0xce7bfe5e…5e58

0x065c9d…c394

6 touches
3 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x0230870e…327e

0x2ab50b…5c41

2 touches
0 conflicts

0x0849cefc…6a65

0x2ab50b…5c41

2 touches
0 conflicts

0x15a8b5e6…0296

0x2ab50b…5c41

2 touches
0 conflicts

0x1cec066a…0d41

0x2ab50b…5c41

2 touches
0 conflicts

0x25267e43…6d09

0x2ab50b…5c41

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