← previous blocknext block →recent activity

Analyzing

Block #74,623,098

12 transactions · 11 stateful · 2026-05-14 22:11:17 UTC

Parallelism

75/100

Blocked

27%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,623,098  ·  12 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0x1da1c6cb…bb3f

0x34b655…2a6f

4 touches
1 conflict

0xfa2527aa…9dd5

0x34b655…2a6f

4 touches
1 conflict

0x8fa7a69c…8fd7

0x2deea0…7777

2 touches
0 conflicts

0xb2ed2298…96e9

0x2deea0…7777

2 touches
0 conflicts

0x2bf6ce2e…282b

0x34b655…2a6f

2 touches
0 conflicts

0x51087f5a…61f7

0x34b655…2a6f

2 touches
0 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity