← previous blocknext block →recent activity

Analyzing

Block #74,762,803

35 transactions · 23 stateful · 2026-05-15 13:43:50 UTC

Parallelism

57/100

Blocked

65%

Avg conflicts / tx

3.03

Longest chain

15 deep

Execution timeline

did this block parallelize well?

view

block #74,762,803  ·  35 txs across 15 waves  ·  depth 15
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

wave w13

wave w14

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

0x512ce80a…9d45

0xd32edf…ff58

29 touches
105 conflicts

0x33018431…8f5c

0x188d58…ea8e

4 touches
1 conflict

0x33018431…8f5d

0x188d58…ea8e

4 touches
1 conflict

0x12309510…0ac2

0x000000…012a

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x33018431…8f5f

0x188d58…ea8e

2 touches
0 conflicts

0x89113341…a1e1

0x188d58…ea8e

2 touches
0 conflicts

0x09000000…0001

0x000000…1000

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

105 conflicts on slot 0x512ce80a4b…889d45

← previous block·next block →recent activity