← previous blocknext block →recent activity

Analyzing

Block #74,484,312

24 transactions · 16 stateful · 2026-05-14 06:39:49 UTC

Parallelism

79/100

Blocked

44%

Avg conflicts / tx

0.58

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,484,312  ·  24 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xf3981be5…2c47

0x34b655…2a6f

10 touches
10 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xbc04d98e…a484

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0xab621973…cc16

0x34b655…2a6f

6 touches
3 conflicts

0xcb63cb0a…66a9

0x34b655…2a6f

4 touches
1 conflict

0x04f0e47d…cb70

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

10 conflicts on slot 0xf3981be56e…f02c47

← previous block·next block →recent activity