← previous blocknext block →recent activity

Analyzing

Block #73,869,259

10 transactions · 8 stateful · 2026-05-11 10:24:55 UTC

Parallelism

60/100

Blocked

38%

Avg conflicts / tx

0.6

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,869,259  ·  10 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

0x00000000…0007

0x1414f3…5137

8 touches
6 conflicts

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x48cb7290…286c

0x1414f3…5137

2 touches
0 conflicts

0x56ce8fd7…b475

0x1414f3…5137

2 touches
0 conflicts

0x7da94aa1…a8e3

0x1414f3…5137

2 touches
0 conflicts

0x9d12029d…d3c9

0x1414f3…5137

2 touches
0 conflicts

0xd9633368…b671

0x1414f3…5137

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: 0x1414f3ba…045137

6 conflicts on slot 0x0000000000…000007

← previous block·next block →recent activity