← previous blocknext block →recent activity

Analyzing

Block #74,423,059

15 transactions · 14 stateful · 2026-05-13 23:52:06 UTC

Parallelism

47/100

Blocked

57%

Avg conflicts / tx

2.33

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,423,059  ·  15 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

16 touches
28 conflicts

0xadac4a86…c2bc

0x34b655…2a6f

14 touches
21 conflicts

0xea02471d…1542

0x34b655…2a6f

14 touches
21 conflicts

0xf3d10975…0d07

0x34b655…2a6f

10 touches
10 conflicts

0xab621973…cc16

0x34b655…2a6f

10 touches
10 conflicts

0xe5e7089a…fb91

0x34b655…2a6f

10 touches
10 conflicts

0xba018e2c…72cd

0x34b655…2a6f

8 touches
6 conflicts

0x4d3e58e0…a2d7

0x34b655…2a6f

6 touches
5 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

28 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity