← previous blocknext block →recent activity

Analyzing

Block #72,426,000

12 transactions · 12 stateful · 2026-05-04 18:00:30 UTC

Parallelism

58/100

Blocked

33%

Avg conflicts / tx

0.5

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,426,000  ·  12 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x8a35acfb…d1ad

0x8d66a4…3095

6 touches
3 conflicts

0xa9988419…9f45

0x34b655…2a6f

6 touches
3 conflicts

0x374426df…f445

0xc8689a…ee79

6 touches
3 conflicts

0xe96c91d2…32ff

0x8d66a4…3095

6 touches
3 conflicts

0xd563f3a1…94b1

0x34b655…2a6f

4 touches
1 conflict

0xef948c34…0463

0x34b655…2a6f

4 touches
1 conflict

0x8a35acfb…d1ac

0x8d66a4…3095

4 touches
1 conflict

0x462c8be7…4f83

0x8d66a4…3095

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: 0x8d66a43f…113095

3 conflicts on slot 0x8a35acfbc1…6bd1ad

← previous block·next block →recent activity