← previous blocknext block →recent activity

Analyzing

Block #74,736,203

38 transactions · 22 stateful · 2026-05-15 10:45:54 UTC

Parallelism

82/100

Blocked

41%

Avg conflicts / tx

0.71

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,736,203  ·  38 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

0xf3aeeb18…90e3

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…0004

0xd5b70d…615b

6 touches
3 conflicts

0x00000000…0002

0xd5b70d…615b

6 touches
3 conflicts

0x00000000…0000

0xd5b70d…615b

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x7c403af1…31b1

0x3bd359…433a

6 touches
3 conflicts

0x18aed20c…48f3

0x000000…012a

6 touches
3 conflicts

0x00000000…0004

0x63e48b…53f2

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 0xf3aeeb189d…8490e3

← previous block·next block →recent activity