← previous blocknext block →recent activity

Analyzing

Block #75,233,103

18 transactions · 16 stateful · 2026-05-17 18:04:27 UTC

Parallelism

78/100

Blocked

31%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #75,233,103  ·  18 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xe6455d1f…1029

0x754704…b603

8 touches
6 conflicts

0x0d0b2509…074d

0x3bd359…433a

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x56a919c4…ab49

0xee8c0e…1242

4 touches
1 conflict

0x12309510…0ac2

0x000000…012a

4 touches
1 conflict

0x3d34f2bd…5d63

0x34b655…2a6f

4 touches
1 conflict

0x6caf33e2…c261

0x34b655…2a6f

4 touches
1 conflict

0x93af5ad2…45f1

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: 0x754704bc…afb603

6 conflicts on slot 0xe6455d1fbe…eb1029

← previous block·next block →recent activity