← previous blocknext block →recent activity

Analyzing

Block #72,286,467

19 transactions · 17 stateful · 2026-05-04 02:30:17 UTC

Parallelism

79/100

Blocked

47%

Avg conflicts / tx

0.68

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #72,286,467  ·  19 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

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0xbad68552…e6bf

0x34b655…2a6f

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0x0de7749d…5bef

0x34b655…2a6f

4 touches
1 conflict

0x374426df…f445

0xc8689a…ee79

4 touches
1 conflict

0x24968e6d…0132

0x065c9d…c394

4 touches
1 conflict

0xa36ce883…837d

0x065c9d…c394

4 touches
1 conflict

0xfbabb02d…af07

0x34b655…2a6f

4 touches
1 conflict

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: Perpl

6 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity