← previous blocknext block →recent activity

Analyzing

Block #75,329,653

6 transactions · 5 stateful · 2026-05-18 04:50:30 UTC

Parallelism

50/100

Blocked

40%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,329,653  ·  6 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

0xde1a0ee7…c75b

0x34b655…2a6f

6 touches
3 conflicts

0x4c20d376…0819

0x34b655…2a6f

6 touches
3 conflicts

0xa6464996…3af9

0x34b655…2a6f

6 touches
3 conflicts

0x363d751e…11ee

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x55227071…0133

0x34b655…2a6f

4 touches
1 conflict

0x746bcce3…d0ce

0x34b655…2a6f

4 touches
1 conflict

0x6f6fc26c…3e34

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 0xde1a0ee72c…10c75b

← previous block·next block →recent activity