← previous blocknext block →recent activity

Analyzing

Block #72,283,087

23 transactions · 16 stateful · 2026-05-04 02:07:33 UTC

Parallelism

70/100

Blocked

44%

Avg conflicts / tx

0.96

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #72,283,087  ·  23 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x59865eee…f1c4

0xd32edf…ff58

13 touches
21 conflicts

0x09106a95…1467

0xeedfbc…f7dc

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x12309510…0ac2

0x000000…012a

2 touches
0 conflicts

0x8f478f26…9d56

0x000000…012a

2 touches
0 conflicts

0x9cafc3b6…ee8c

0x000000…012a

2 touches
0 conflicts

0xdf30cbec…e9dc

0x000000…012a

2 touches
0 conflicts

0xe619d904…3256

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: 0xd32edf66…9fff58

21 conflicts on slot 0x59865eee49…15f1c4

← previous block·next block →recent activity