← previous blocknext block →recent activity

Analyzing

Block #73,261,588

13 transactions · 11 stateful · 2026-05-08 14:44:55 UTC

Parallelism

77/100

Blocked

36%

Avg conflicts / tx

0.46

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,261,588  ·  13 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…0002

0xab3526…fa38

6 touches
3 conflicts

0xbd7e37a9…9eb5

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x568e39bf…db05

0x065c9d…c394

2 touches
0 conflicts

0x63d7b3f1…de55

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0013

0x1b6862…e19c

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: 0xab35264b…1cfa38

3 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity