← previous blocknext block →recent activity

Analyzing

Block #74,331,625

18 transactions · 15 stateful · 2026-05-13 13:43:41 UTC

Parallelism

67/100

Blocked

40%

Avg conflicts / tx

0.89

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,331,625  ·  18 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

0xf3981be5…2c47

0x34b655…2a6f

12 touches
15 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xe5e7089a…fb91

0x34b655…2a6f

6 touches
3 conflicts

0x2d5e3771…9a87

0x34b655…2a6f

6 touches
3 conflicts

0x4a6a2a1a…c177

0x34b655…2a6f

6 touches
3 conflicts

0x4d3e58e0…a2d7

0x34b655…2a6f

6 touches
3 conflicts

0xa3ff1ab2…8ae3

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