← previous blocknext block →recent activity

Analyzing

Block #74,762,100

12 transactions · 9 stateful · 2026-05-15 13:39:08 UTC

Parallelism

83/100

Blocked

22%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,762,100  ·  12 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

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xfbbc35e2…f66b

0x34b655…2a6f

4 touches
1 conflict

0x5d70606a…1d53

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…7212

0x34b655…2a6f

4 touches
1 conflict

0x348fda08…7e96

0x065c9d…c394

2 touches
0 conflicts

0x443a3e47…f4a4

0x065c9d…c394

2 touches
0 conflicts

0x8a06e274…9522

0x065c9d…c394

2 touches
0 conflicts

0x8e7c62ec…2fd5

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity