← previous blocknext block →recent activity

Analyzing

Block #74,481,410

20 transactions · 14 stateful · 2026-05-14 06:20:30 UTC

Parallelism

65/100

Blocked

50%

Avg conflicts / tx

1.1

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,481,410  ·  20 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xcb76dcbf…e108

0xd32edf…ff58

13 touches
21 conflicts

0x5860c4f3…0c39

0x3bd359…433a

4 touches
1 conflict

0x00000000…0000

0x690fd4…e995

4 touches
1 conflict

0x00000000…0002

0x690fd4…e995

4 touches
1 conflict

0x00000000…0003

0x690fd4…e995

4 touches
1 conflict

0x00000000…0000

0xbab229…9388

4 touches
1 conflict

0x00000000…0001

0xbab229…9388

4 touches
1 conflict

0x00000000…0003

0xbab229…9388

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

21 conflicts on slot 0xcb76dcbf6e…55e108

← previous block·next block →recent activity