← previous blocknext block →recent activity

Analyzing

Block #74,649,249

9 transactions · 6 stateful · 2026-05-15 01:05:32 UTC

Parallelism

78/100

Blocked

17%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,649,249  ·  9 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x2f7781d6…e632

0x34b655…2a6f

4 touches
1 conflict

0x97d5efed…1aa4

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x24968e6d…0132

0x065c9d…c394

2 touches
0 conflicts

0xaff6435a…fa04

0x065c9d…c394

2 touches
0 conflicts

0xb55cea61…1198

0x065c9d…c394

2 touches
0 conflicts

0xbc58e764…81c5

0x065c9d…c394

2 touches
0 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

1 conflict on slot 0x2f7781d6c5…16e632

← previous block·next block →recent activity