← previous blocknext block →recent activity

Analyzing

Block #72,394,564

8 transactions · 6 stateful · 2026-05-04 14:30:58 UTC

Parallelism

75/100

Blocked

17%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,394,564  ·  8 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

0x0efc210e…70ab

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x06ac540a…ad20

0x34b655…2a6f

2 touches
0 conflicts

0x1b5d2e60…99b5

0x34b655…2a6f

2 touches
0 conflicts

0x2343b4c2…d6bb

0x34b655…2a6f

2 touches
0 conflicts

0x5ce2465f…c4f1

0x34b655…2a6f

2 touches
0 conflicts

0x97b0b2ee…4666

0x34b655…2a6f

2 touches
0 conflicts

0x9e719c7a…df63

0x34b655…2a6f

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: 0x34b6552d…112a6f

1 conflict on slot 0x0efc210ee8…0e70ab

← previous block·next block →recent activity