← previous blocknext block →recent activity

Analyzing

Block #75,478,963

33 transactions · 19 stateful · 2026-05-18 21:28:05 UTC

Parallelism

73/100

Blocked

47%

Avg conflicts / tx

1.12

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #75,478,963  ·  33 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x6481285a…8190

0xd32edf…ff58

17 touches
36 conflicts

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x18aed20c…48f3

0x000000…012a

4 touches
1 conflict

0xda6b535e…6d67

0x1b6862…e19c

4 touches
1 conflict

0x7c403af1…31b1

0x3bd359…433a

4 touches
1 conflict

0x00000000…0000

0xd5b70d…615b

4 touches
1 conflict

0x00000000…0003

0xd5b70d…615b

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

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: 0xd32edf66…9fff58

36 conflicts on slot 0x6481285a90…5f8190

← previous block·next block →recent activity