← previous blocknext block →recent activity

Analyzing

Block #74,266,392

20 transactions · 19 stateful · 2026-05-13 06:29:45 UTC

Parallelism

55/100

Blocked

42%

Avg conflicts / tx

1.8

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,266,392  ·  20 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x54553c5d…7039

0x188d58…ea8e

18 touches
36 conflicts

0x12309510…0ac2

0x000000…012a

18 touches
36 conflicts

0x33018431…8f5c

0x188d58…ea8e

18 touches
36 conflicts

0x33018431…8f5d

0x188d58…ea8e

18 touches
36 conflicts

0x54553c5d…7038

0x188d58…ea8e

18 touches
36 conflicts

0x0dbf9688…c6cf

0x9c82eb…cd90

18 touches
36 conflicts

0x59556eb7…c000

0x9c82eb…cd90

18 touches
36 conflicts

0x983a5d61…9766

0x57ea24…2cec

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: 0x188d586d…f9ea8e

36 conflicts on slot 0x54553c5d2b…797039

← previous block·next block →recent activity