← previous blocknext block →recent activity

Analyzing

Block #72,228,167

9 transactions · 8 stateful · 2026-05-03 19:58:25 UTC

Parallelism

78/100

Blocked

13%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,228,167  ·  9 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

0x8a35acfb…d1ab

0x8d66a4…3095

4 touches
1 conflict

0x96504a63…52d2

0x8d66a4…3095

4 touches
1 conflict

0x6bd9b2de…7d72

0x0f2610…0edc

2 touches
0 conflicts

0x48cb4b9b…2417

0x2185cd…21c7

2 touches
0 conflicts

0x5eba4d17…0176

0x2ae0cf…3d4e

2 touches
0 conflicts

0xdc6d8124…dbb8

0x2ae0cf…3d4e

2 touches
0 conflicts

0xdc6d8124…dbbd

0x2ae0cf…3d4e

2 touches
0 conflicts

0xdc6d8124…dbbe

0x2ae0cf…3d4e

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

1 conflict on slot 0x8a35acfbc1…6bd1ab

← previous block·next block →recent activity