← previous blocknext block →recent activity

Analyzing

Block #74,389,088

15 transactions · 9 stateful · 2026-05-13 20:06:01 UTC

Parallelism

60/100

Blocked

56%

Avg conflicts / tx

1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,389,088  ·  15 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0x1c389468…6b0e

0x34b655…2a6f

12 touches
15 conflicts

0xa678cb89…4abd

0x34b655…2a6f

10 touches
10 conflicts

0x5c0e5bb8…4f6e

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xf3d10975…0d07

0x34b655…2a6f

6 touches
3 conflicts

0xfe3d37ee…6e67

0x34b655…2a6f

6 touches
3 conflicts

0xd895ee0b…d301

0x34b655…2a6f

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity