← previous blocknext block →recent activity

Analyzing

Block #74,392,262

28 transactions · 15 stateful · 2026-05-13 20:27:07 UTC

Parallelism

86/100

Blocked

40%

Avg conflicts / tx

0.32

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,392,262  ·  28 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

0x1c389468…6b0e

0x34b655…2a6f

6 touches
3 conflicts

0x5c0e5bb8…4f6e

0x34b655…2a6f

6 touches
3 conflicts

0x77100a2a…91a4

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x99a3a7c1…1e2b

0x0cc9b2…7777

4 touches
1 conflict

0x9b36f19f…fa5a

0x34b655…2a6f

4 touches
1 conflict

0xbc04d98e…a484

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: 0x34b6552d…112a6f

3 conflicts on slot 0x1c38946843…a16b0e

← previous block·next block →recent activity