← previous blocknext block →recent activity

Analyzing

Block #73,696,191

13 transactions · 10 stateful · 2026-05-10 15:02:44 UTC

Parallelism

77/100

Blocked

20%

Avg conflicts / tx

0.23

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,696,191  ·  13 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0xe96c91d2…32ff

0x8d66a4…3095

4 touches
1 conflict

0x7f430e47…4cbd

0x8d66a4…3095

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x197ad861…6bb3

0x065c9d…c394

2 touches
0 conflicts

0x2ccf95be…d87c

0x065c9d…c394

2 touches
0 conflicts

0x34120ee9…2709

0x065c9d…c394

2 touches
0 conflicts

0x7291fa50…c11f

0x065c9d…c394

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

3 conflicts on slot 0x8a35acfbc1…6bd1ab

← previous block·next block →recent activity