← previous blocknext block →recent activity

Analyzing

Block #75,196,408

14 transactions · 12 stateful · 2026-05-17 13:59:21 UTC

Parallelism

79/100

Blocked

17%

Avg conflicts / tx

0.21

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,196,408  ·  14 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

0xee576a92…fe14

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x3e5aa7fb…0f15

0x34b655…2a6f

4 touches
1 conflict

0x463be44a…2830

0x34b655…2a6f

4 touches
1 conflict

0x6713b018…05f3

0x34b655…2a6f

4 touches
1 conflict

0x8a5efe9a…fa31

0x34b655…2a6f

4 touches
1 conflict

0x86cea35b…bdff

0x34b655…2a6f

4 touches
1 conflict

0x9dccd2a9…2790

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

3 conflicts on slot 0xee576a924c…75fe14

← previous block·next block →recent activity