← previous blocknext block →recent activity

Analyzing

Block #74,722,562

16 transactions · 14 stateful · 2026-05-15 09:14:41 UTC

Parallelism

56/100

Blocked

50%

Avg conflicts / tx

1.38

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,722,562  ·  16 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

0xdc158dc7…91ac

0xd32edf…ff58

13 touches
21 conflicts

0x8c49c85c…ee96

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0xf6802cf0…344f

0x000000…012a

2 touches
0 conflicts

0x56a919c4…ab49

0x01bff4…1071

2 touches
0 conflicts

0x78eb0de5…1db2

0x01bff4…1071

2 touches
0 conflicts

0x703b861a…cbe3

0x188d58…ea8e

2 touches
0 conflicts

0x703b861a…cbe4

0x188d58…ea8e

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 0xdc158dc736…5591ac

← previous block·next block →recent activity