← previous blocknext block →recent activity

Analyzing

Block #74,736,345

26 transactions · 20 stateful · 2026-05-15 10:46:51 UTC

Parallelism

77/100

Blocked

50%

Avg conflicts / tx

0.92

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,736,345  ·  26 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

0x801a6e57…d85c

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xea02471d…1542

0x34b655…2a6f

10 touches
10 conflicts

0xf3d10975…0d07

0x34b655…2a6f

8 touches
6 conflicts

0xe5e7089a…fb91

0x34b655…2a6f

8 touches
6 conflicts

0xf3d7a307…4d63

0x065c9d…c394

8 touches
6 conflicts

0x97b0b2ee…4666

0x34b655…2a6f

7 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

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 0x801a6e5726…c1d85c

← previous block·next block →recent activity