← previous blocknext block →recent activity

Analyzing

Block #72,861,063

13 transactions · 12 stateful · 2026-05-06 18:19:50 UTC

Parallelism

85/100

Blocked

17%

Avg conflicts / tx

0.15

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,861,063  ·  13 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x7f189cf6…afab

0x065c9d…c394

4 touches
1 conflict

0x1da1c6cb…bb3f

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x356ac916…a5f9

0x065c9d…c394

3 touches
1 conflict

0xbcc1b459…f94f

0x3bd359…433a

2 touches
0 conflicts

0x377b0dec…4b11

0x405b63…7777

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

1 conflict on slot 0x7f189cf621…beafab

← previous block·next block →recent activity