← previous blocknext block →recent activity

Analyzing

Block #72,860,215

15 transactions · 13 stateful · 2026-05-06 18:14:10 UTC

Parallelism

73/100

Blocked

23%

Avg conflicts / tx

0.4

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #72,860,215  ·  15 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x596dc94b…e09e

0x065c9d…c394

6 touches
3 conflicts

0x7f189cf6…afab

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x96cd1f8a…5351

0x065c9d…c394

3 touches
1 conflict

0x06da6418…53ef

0x065c9d…c394

2 touches
0 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x7f8fcaec…2b0a

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: 0x065c9d28…a9c394

3 conflicts on slot 0x596dc94bbb…1be09e

← previous block·next block →recent activity