← previous blocknext block →recent activity

Analyzing

Block #74,485,287

36 transactions · 22 stateful · 2026-05-14 06:46:19 UTC

Parallelism

81/100

Blocked

41%

Avg conflicts / tx

0.67

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,485,287  ·  36 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

0xdd432de1…026d

0xd32edf…ff58

13 touches
21 conflicts

0x0b6d25a1…2e3b

0x34b655…2a6f

4 touches
1 conflict

0x38dee07f…7598

0x34b655…2a6f

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0xadac4a86…c2bc

0x34b655…2a6f

4 touches
1 conflict

0x00000000…001c

0x1b6862…e19c

2 touches
0 conflicts

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 0xdd432de1a1…33026d

← previous block·next block →recent activity