← previous blocknext block →recent activity

Analyzing

Block #73,324,294

10 transactions · 9 stateful · 2026-05-08 21:42:17 UTC

Parallelism

70/100

Blocked

22%

Avg conflicts / tx

0.3

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,324,294  ·  10 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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0xf537eaa0…73c8

0x065c9d…c394

4 touches
1 conflict

0xa27fa22d…7dca

0x54cd53…9e7d

2 touches
0 conflicts

0xd1a0adf6…6e55

0x54cd53…9e7d

2 touches
0 conflicts

0x01c1aa1e…5bd4

0x6657d1…8ccc

2 touches
0 conflicts

0x0219b198…cdce

0x6657d1…8ccc

2 touches
0 conflicts

0x039fa778…e0bd

0x6657d1…8ccc

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 0x0000000000…00003d

← previous block·next block →recent activity